I have an interesting question and wanted to check if this is practically and technically possible. I have a 9.3.1 geodatabase thats MS SQL that i need to keep in sync with a publications 10.4.1 database - MS SQL. Also i need to keep the 10.4.1 publications database in sync with another 10.4.1 edits database. So in total there are 3 enterprise geodatabase in place.
Has anyone attempted anything similar in the past?
My main concerns is with the number of bidirectional replications if anything would be affected. As long as i time then in the right sequence i think should be ok but just wanted to check and if anyone has a better way.
Performing geodatabase replication from a lower release geodatabase (9.3.1) to a higher one, or same release should be fine. But replicating from a higher release to a lower one is not recommended, as the higher release geodatabase may have functionality not supported/available in the lower release geodatabase. Please see this help topic,
Hope this helps,
So the editing will be done in the 9.3.1 gdb and the 10.4.1 edits geodatabase only?
And you plan to use the 9.3.1 gdb and the 10.4.1 edits geodatabase as the Parent gdb & the 10.4.1 publication gdb as the Child in both cases?