AnsweredAssumed Answered

Using Versioning / Archive to keep database history

Question asked by shahar04 on Sep 4, 2014
Latest reply on Sep 4, 2014 by jskinner-esristaff

Hello all,

 

Part of my organisation's gis data is stored in an SQL Server Geodatabase, within a single dataset that contains dozens of simple feature classes.

Twice a year we receive an update package that contains the latest version of those feature classes. I used to overwrite the existing data with the new package while keeping the old data in a File Geodatabase. 

I want to be able keep the data in our SQL Server Geodatabase and to able to see how the data looked like at a certain point in the past. I thought about using Geodatabase archiving but I'm not sure how to insert the new update package. Should I delete the rows of the feature classes and then append the new data? Should I use "Load data"? Is there some other way?

 

******************

Technical info:

1. SQL Server 2012.

2. ArcGIS 10.2.1.

3. The new data doesn't change schema / feature class structure.

4. Most of the data doesn't change at all.

5. The new data contains all sorts of changes: added features, deleted features, feature-shape changes, attribute changes and so on.

Outcomes