Has anyone had success in migrating Branch Versioned Datasets to a new database instance while maintaining branch history?
We are working through a migration from a Windows Server 2019 hosted PostgreSQL 15 instance into a PostgreSQL 15 RDS instance in AWS and have had some trouble maintaining branch history with cross-database copy workflows.
Ultimately we are looking to maintain the ability to rollback to a historical moment in our new database, but would prefer to keep things in the same active table. We are aware of this lovely article outlining the ability to do so from a dedicated archive table which we could migrate to the instance as a net-new table but wanted to confirm if our desired workflow was possible.
Things we've tried:
- Full ArcGIS-based Copy/Paste (ArcGIS Pro) -- no historical rows brought over
- Truncate/Append into a branch-version-enabled copy of the table in the RDS instance (ArcGIS Pro) -- no historical rows brought over
- Append of Archive table records into destination table in RDS (ArcGIS Pro) -- Resulted in all clients showing a total of all records AND their respective historical moments
Thanks in advance for any insight!
