Multiple Two-way replicas - Deletes not syncing across replicas

384
1
Jump to solution
02-12-2019 07:58 AM
KimberlyWhitney
New Contributor

I am managing an SDE database across multiple sites. I have a parent database with a two-way replica at two different sites.  When synchornizing changes to the parent and then back down to the children, the deletes from on replica do not make it into the second replica.  What is the customary way to set up a sde workflow in which multiple sites will need to work and receive changes from a single parent database each day?  Is this a known problem that deletions will not sync across multiple two-way replicas built from the same parent?

0 Kudos
1 Solution

Accepted Solutions
KimberlyWhitney
New Contributor

In case others run into this problem, it is due to the order of operations in which syncs and maintenance are performed.  To properly sync databases across sites, i now follow this order:

1. Send edits from all children to the parent using: Geodatabase 2 > 1

2. Parent Maintenance: After all children have synced to the parent.

   a. Compress the parent database

   b. Analyse the parent database

   c. Rebuild Indexes on the parent database

3. Send edits from parent to all children. using: Geodatabase 1 > 2

4. Child Maintenance: On all Children after sync

   a. Compress child database

   b. Analyse child database

   c. Rebuild Indexes on child database

View solution in original post

1 Reply
KimberlyWhitney
New Contributor

In case others run into this problem, it is due to the order of operations in which syncs and maintenance are performed.  To properly sync databases across sites, i now follow this order:

1. Send edits from all children to the parent using: Geodatabase 2 > 1

2. Parent Maintenance: After all children have synced to the parent.

   a. Compress the parent database

   b. Analyse the parent database

   c. Rebuild Indexes on the parent database

3. Send edits from parent to all children. using: Geodatabase 1 > 2

4. Child Maintenance: On all Children after sync

   a. Compress child database

   b. Analyse child database

   c. Rebuild Indexes on child database