topic Multiple Utility Network Datasets in an Instance in Electric Questions

Multiple Utility Network Datasets in an Instance

EdwardBlair — Thu, 27 Dec 2018 21:45:41 GMT

I now have one utility network dataset in a SQLExpress instance - this one has pipeline and structure domains. Will it be OK if I create another utility network dataset in the same instance - the new one to have an electric and structure domains? These datasets will cover different geographies and have different spatial references.

What I'm concerned about is the structure domains. Will there be a naming conflict for the two sets of structure feature classes?

Any pointers would be appreciated.

Thx,
Ed

Re: Multiple Utility Network Datasets in an Instance

PaulLeBlanc1 — Thu, 27 Dec 2018 21:54:24 GMT

The StructureNetwork for the 2nd UN will have _# suffixes added to ensure unique names.

With that being said, there could be conflicts with coded value domains. Don't share asset type domains across multiple utility networks.

Re: Multiple Utility Network Datasets in an Instance

RichardDumont — Wed, 02 Jan 2019 16:07:25 GMT

I had the same concerns Ed, I have not had a chance to dig into it to form a good question, thanks for asking. So it sounds like, if you have for example, which is what I was thinking about, an Electric Structure and a Gas Structure it would be best to keep these separated of course, so you really need to plan this out to not cause issues down the road.

Re: Multiple Utility Network Datasets in an Instance

EdwardBlair — Wed, 02 Jan 2019 16:41:40 GMT

Rich -

Thanks for the note. For my current purposes I just created a new SQLServer instance to hold my second (electric) dataset. Seems to work fine.