nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

14 Million Associations - Best way to load to Utility Network?

CristinHolmgren2

UNv7 ArcGIS Pro 3.5

I have an asset package with about 14 million associations. The usual method of creating a UN from an AP (Asset Package To Geodatabase) is struggling with the volume of these associations (I think). I've done some online research, but cannot seem to find a good way to break these up. I did find some suggestions eluding to breaking up the C_Associations table into many table and using the first one 'C_Associations' to build the UN and then add the UN association table (as a view) from the new UN (mobile geodatabase) and then append the other smaller association tables into that.

In theory, that sounds easy enough, but the AP associations table and the UN associations table are formatted very differently. I'm hoping someone has encountered this situation as well.

@RobertKrisher ?

Find more posts tagged with

Accepted answers

MikeMillerGIS

Asset Package to GDB probably has the fastest path to import associations as when we create the UN we delay adding attribute rules, relationship classes and other things that trigger more expensive GDB behavior until after import association is done.

All comments

MikeMillerGIS

CristinHolmgren2

Thanks, Mike. That's what I'm using. I can't tell if anything is happening anymore. Its just parked at 1% on step 16. I have this running on a big machine, too. I've done all the cleansing of the associations prior to running this that I could think of. Do I just need to wait it out?

RobertKrisher

@CristinHolmgren2 are you deploying this to a mobile geodatabase? or a file geodatabase? or enterprise geodatabase?

Don't use a file geodatabase when working with associations, they are painfully slow for that. If you are using a mobile geodatabase, make sure it is on an SSD that is local to the machine that is running the tool.

You could turn on simple build logging to see timestamps of when the various events are running.

JohnAlsup

I routinely import using the method Mike suggested and I'm loading more than 20 million associations and it generally takes under two hours for that part.

CristinHolmgren2

Thanks to @MikeMillerGIS @JohnAlsup @RobertKrisher for the responses!

After struggling with 4/5 hr stalled runs yesterday and finally reaching out for help, I ended up kicking off the process again (on 2 different machines) and just let it go overnight.

Both runs of course have now finished up - successfully and in about 2 - 2.5 hrs. I didn't change anything about the process except that I wasn't monitoring it.

All of your comments and recommendations were already included in the process but its good to know that I am using the correct tools, formats and am within the acceptable association range as well.

Thanks again for taking the time to respond.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.