ObjectID's change when editing

Discussion created by zenben on Sep 5, 2012
Latest reply on Jan 10, 2013 by zenben
I recently upgraded our entire system from 10.0 to 10.1. We have a SQL Server 2008 R2 sde geodatabase and Desktop 10.1.

In the first major edit I did after the upgrade, I updated attributes on about 100 trees in our sde geodatabase. I noticed that ArcMap changed the ObjectID for the trees I edited. Note: these were existing trees that already had ObjectID's, all I did was update attributes.

The other new thing I've been doing is using a replica of the database on another server, so I put Global ID's in all my datasets. I've been seeing hints in other places that if GlobalID's are in use that it may change how ObjectID's are handled, but I can't find any direct documentation or explanation of that.

One immediate effect is that the ObjectID's in my local parent geodatabase are DIFFERENT from the objectID's for the same features in the child replica even after synchronizing.

Thanks for any explanation or resources you can offer to help me understand what is going on.