ArcSDE Geodatabase Schema Changes & Replication Conflicts

09-01-2015 01:03 PM
Occasional Contributor


I've looked through the Help, but haven't found anywhere that answers this question (though I certainly may have missed it).  If you have a central ArcSDE enabled database, such as in SQL Server, which has multiple Check Out replicas, I am curious as to what is necessary to make schema changes.  If I was to make schema changes (such as adding fields in tables or feature classes), would I need to first check in any outstanding replicas?  Or, could I make those changes and check in existing replicas afterwards?  I cannot tell if that would be possible, or if the synchronize changes tool would fail to account for those changes and not run.  Has anyone dealt with this?



0 Kudos
0 Replies