Skip to main content
Solved

Reading/Writing SDE Archived featureclasses

nordpil
Supporter
Forum|alt.badge.img+10

I have MSSQL ESRI Entrerprise Geodatabases that are non-versioned but have archiving enabled. As far as I have figured out, there are no ESRI tools that easily copy data with the full archive of the feature class.

If it was versioned I could use the ESRI tools for replication…

What is the current best methods for an operation like this?

Best answer by nordpil

​@bwn unversioned featureclasses have the archive in the same table, it has GDB_FROM_DATE and GDB_TO_DATE that delimit when a feature has been valid. Reading archive history one can do in an ArcSDE reader (using archive where clause) or any MSSQL reader.

Workflow I have so far:

  • Export xml workspace document without data (esri tool) for featureclass I want to migrate
  • Import xml workspace into new egdb (also ESRI tool)
  • Then one needs to update the featureclasses in the new egdb to set archiving enabled for the target featureclasses (that have archiving in the source)
  • A simple read/write FME operation using MSSQL Spatial reader/writer
    • feature classes first
    • relational tables second
  • This seems to work fine, except that the OBJECTID’s reference for new features in the egdb will be out of sync, but it seems to doable to check out new OBJECTIDs using the esri stored procedures to work around it

(haven’t looked at attachments yet)

View original
siennaatsafe
B
2 people upvoted this
  • siennaatsafe
    siennaatsafe
  • B
    bob123
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

bwn
Evangelist
Forum|alt.badge.img+26
  • bwnEvangelist
  • Evangelist
  • January 20, 2025

You can read the archive / “History” directly with a Microsoft SQL Server Spatial or Non-Spatial Reader.

They will be the same table name as the base table, but with “_H” appended.  You can see the table name in ArcCatalog

 

 

nordpil
Supporter
Forum|alt.badge.img+10
  • nordpilSupporter
  • Author
  • Supporter
  • Best Answer
  • January 21, 2025

​@bwn unversioned featureclasses have the archive in the same table, it has GDB_FROM_DATE and GDB_TO_DATE that delimit when a feature has been valid. Reading archive history one can do in an ArcSDE reader (using archive where clause) or any MSSQL reader.

Workflow I have so far:

  • Export xml workspace document without data (esri tool) for featureclass I want to migrate
  • Import xml workspace into new egdb (also ESRI tool)
  • Then one needs to update the featureclasses in the new egdb to set archiving enabled for the target featureclasses (that have archiving in the source)
  • A simple read/write FME operation using MSSQL Spatial reader/writer
    • feature classes first
    • relational tables second
  • This seems to work fine, except that the OBJECTID’s reference for new features in the egdb will be out of sync, but it seems to doable to check out new OBJECTIDs using the esri stored procedures to work around it

(haven’t looked at attachments yet)

Most helpful members this week

Community Stats

30,859
Posts
116,996
Replies
38,689
Members
Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.