Duplicate Global IDs in Separate Feature Classes Using Export/Import XML Workspace Document

LRoberts_RDM

We have a geodatabase with two schema owners. We will call them DBO and TN. We want to consolidate all of our feature classes to TN. The DBO feature classes have attachments and relationship classes setup.

We are able to use the Export to XML Workspace Document from the DBO connection and then Import from XML Workspace Document using the TN connection. This creates exact duplicates (including Global Ids) of the feature classes with all of the attachments and relationship classes intact, but with TN as the schema owner. 

My question is if we then delete all of the DBO feature classes, will we run into any issues down the road if we have duplicate IDs for a small amount of time?

Mike_Redpath

GlobalIDs are only required to be unique within a given table or feature class. There is no geodatabase‑wide GlobalID registry or sequence.

When you export and import via an XML Workspace Document, GlobalIDs are intentionally preserved so that attachments and relationship classes remain intact. Having two copies of a dataset under different schema owners that temporarily contain the same GlobalID values is expected and supported.

Deleting the original DBO feature classes after validation will not cause issues, as the TN feature classes are independent database objects with their own constraints and metadata.