We are building an application with several spatial tables, provided by a commercial vendor, at its core. The vendor provides updates quarterly. We maintain several tables of our own, derived from these commercial tables. Our application would benefit from versioning the commercial tables along with our derived tables, such that we can see a consistent view of things at any point in time.

Upon each update from the vendor, I would like to "diff" the changes and apply them to our database, then update our derived tables accordingly. Can this be accomplished with ESRI's implementation of versioning? Would this require registering our tables with the GDB? (I prefer to do the heavy lifting with PL/SQL, so I'm not sure how I feel about this.)


1 Answer 1


If I understand your question corrrectly IMO the answer is no. Versioning simply stated tracks changes to existing data within the database.

I used to use a modelbuilder script to check incoming shape files for "diff" in both the spatial and attributes, make a selection of the new differing data and then export that to a seperate file for import to my db.

There is a script available to check two sde layers.

For more on versioning (in case you are interested)
system tables
Quick view of versioning
Long and short transaction support
Data maintenance transactions

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.