I have "Edit" and "Publish" enterprise geodatabases (SQL Server 2014) with a one-way replica from Edit to Publish. Some feature classes are maintained by users with their own copies in other locations (file gdb, .shp) so I have a script that finds updated copies, runs Delete Features / Append to update the Edit geodatabase and then Syncronize Changes to update the Publish geodatabase. This process will not reset the OBJECTID's back to 0, so they will continue to accumulate every time I run the process. I don't know if this will be a problem in the future or not but I don't really like it. Is there a way to get the OBJECTID to reset to 0 in this process without having to unregister the feature class as versioned (to use Truncate), which I think would also require me to re-establish the replica? Running a "compress database" after Delete Features didn't work.