I can't really see what is new here in 9.4.
This technical article:
http://support.esri.com/index.cfm?fa=knowledgebase.techarticles.articleShow&d=34200
describes how you can setup one way child to parent replicas and it was already there for 9.0. What does 9.4 add to this?
I was hoping the new thing in 9.4 would be that there is no need to copy all data into the parent first. It is the moving of data with globalIDs that I would like to avoid. We have a set of 'orphan' child geodatabases without a parent. I would like a parent GDB simply to 'adopt' these child GDBs and accept data from them. The initial sync, or setting up the replication, would get all existing data from the child GDB tables and feature class into the parent.
Pasi
We have a set of 'orphan' child geodatabases without a parent. I would like a parent GDB simply to 'adopt' these child GDBs and accept data from them.
Pasi
The solution we ended up using was to setup separate one-way parent to child replicas from the remote sde geodatabase into file geodatabase in the central office. So each one has its own parent, or target, FGDB. We then have a python script that combines the data from all those replica fgdbs into a central sde geodatabase.
That python that combines data isn't changes only, it simply reloads the data in sde from those fgdbs.Takes few hours to run but that is ok as a nightly task.
Advantage of that is it is very simple (the simplest possible replication scenario) and in case anything goes wrong with one replica we can just re-create that without affecting others.