Geodatabase maintenance

LeoDonahue — Mon, 26 Aug 2013 14:13:46 GMT

How many of us have data in projection A in SDE1, but need to publish it in projection B in SDE2?

Of the data in projection A, if it is versioned and participates in a replica, you need a way to reconcile/post, synchronize changes for your data. Then I supposed you have a staging geodatabase that you project from projection A to projection B. Then I suppose you have a routine that deletes features from SDE2 and appends features from the staging geodatabase.

Now, you can write a script that does this in batch, and it might take an hour or more depending on the size of your featureclasses and how many there are. But what if you only want to update a single featureclass in this process? Are we really still at the point where we have an individual script for every single featureclass that we might want to run through this process? Plus a batch script?

The only thing that varies in this process is the featureclass name.

Before I set out to write my own tool to do this, how are the rest of you handling this?

I realize that a universal tool is hard to build because everyone has a different setup. But if I may make this jab on a Monday morning, it seems as though ESRI gives us really cool tools and over the years likes to tell us what we can and can't do with the cool tools - mostly by deprecating them (the sde stuff, the changes in ArcGIS Server, etc). I just assumed that by now we would have a graphical tool in ArcCatalog that shows us the fc's that participate in a replica and have some way to process them in batch or individually, based on our setup.

topic Geodatabase maintenance in Data Management Questions

Geodatabase maintenance