Migrating UN from one geodatabase to another geodatabase using a different RDBMS

[AnthonyRyanEQL]

Hi there,

I'm looking at the documentation on Utility network dataset administration—ArcGIS Pro | Documentation about how to migrate a utility network dataset.

I'm trying to figure out how would I migrate from a geodatabase on AWS SQL Server RDS to HANA geodatabase on AWS infrastructure as well.

The documentation talks about export/inport using the XML workspace document from the dataset. Does this process include all of the associated/logically feature classes (eg. associations, etc) ? This would also be the same of the note mentioning the core copy & paste tools

Thanks

[JohnAlsup]

Personally I would use the Apply Asset Package tool for creating and loading the initial data in to your Target UN.  The tool is RDBMS agnostic.

I would also start with one of the esri foundation UN models.

Once your UN database is setup and loaded, the foundation documentation walks you through the process of enabling, versioning, publishing, etc.  

The foundation solutions are found on the Esri Solutions site solutions.esri.com

[AnthonyRyanEQL]

John,

We have been using UN electric for the past 2 years in PRD so I'm looking into how to migrate an existing PRD UN which will be part of an ArcGIS Enterprise upgrade as well?

[JohnAlsup]

Then I would export to Asset Package and import that packing using the Apply Asset Package.  In my opinion, that is the safest, fastest path.

[RobertKrisher · Accepted solution]

I agree with John that the export/import asset package is likely going to be the fastest, most reliable way to transfer the data, especially if you have a lot of associations. My second choice would be copy/paste because of the ease-of-use but given the size of your database it may take some time to do the transfer. The import/export xml workspace document is a great way to transfer schema between databases, but if you are moving a sizable amount of data, it's not a very good option because of the size of the xml file involved.

[AnthonyRyanEQL]

Our UN has approx. 15M features with 24M associations. It's the Energy Queensland implementation that was showcased in the 2022 UC

[aperi]

What if we have to replicate daily on a schedule and not just one time, to a different eGBD for read-only access to other ERP Systems consuming the UN data? FME? RDBMs tools ( backup /restore?)
Thoughts? @RobertKrisher @JohnAlsup 

[JohnAlsup]

RDMBS replication for a UN would very difficult to configure.  I doubt it would be successful.  The Esri Solutions tool, Utility Data Management Support (UDMS) contains a tool named Export Reporting Data.  This tool will copy data from a UN to an Enterprise Geodatabase and create views with joins to the associations table so you can build views, for example from devices to structures.  These views can be setup one time and then you can execute Export Reporting Data daily replacing data in the target database without affecting the views.  Then you are able to run SQL type queries against non-versioned data (as the versions are not copied out).  The only drawback is that you cannot trace on this database.

https://github.com/Esri/Utility-Data-Management-Support-Tools?tab=readme-ov-file

https://esri.github.io/Utility-Data-Management-Support-Tools/docs/3.5/

[RobertKrisher]

@aperi read this article for more information about one-way feature service-to-feature service sync capabilities: One-way feature service-to-feature service sync for simple features. For a full utility network, you can use any of the approaches you mentioned above depending on your requirements.

[aperi]

Thank You @JohnAlsup  and @RobertKrisher