Should I make a Child Replica for this set up?

AlyssaWood

I'm kind of new at working with Enterprise Geodatabases and I'm setting this all up by myself so I'm not sure if this is the route to go. We are working in 3 states and I want a different Database for each state - it will just make all of our editing and field work a lot easier to manage. However, I want them to all have the same schema and I am still making quite a few changes to the DB schema while we work through some issues and figuring out the best set up. Instead of needing to import an XML every time, I'm wondering if I should just make one Blank DB with the schema that I do all my schema edits on, then make all my 'production' DB's Child replicas so they will see the changes? We are using SQL Server as our DBMS if that helps.

I'm hoping someone has a simpler suggestion, cause I don't ever want to make a mistake like Syncing changes and then they all suddenly have data from one state that I didn't want there. 

TIA for the help or suggestions!

Asrujit_SenGupta

Hello..

Yes, Replication can be useful for your scenario. For Replication, you will need always one Parent gdb and one Child gdb. However the Parent can't be blank with only schema, like you suggested.

• The Parent SDE gdb can be the main one with all your data (Data from all 3 States).
• Each State can then be given a Child sde geodatabase, which will contain only data for that State.
• You can then setup One-way Child to Parent replication, so that updated data is sent from each Child gdb to the parent only. (** If you don't need data restriction, you can also setup Two-way replication between all the 4 GDBs, with the full data)

Replica schema changes 

Note: You can do schema changes for existing data which is part of the replica, but you won't be able to add new Feature Classes/Table to existing replica.