Múltiplos Conjuntos de Dados de Utility Network em uma Instância

Question

<\/HEAD>Agora eu tenho um conjunto de dados de utility network em uma instância SQLExpress - este possui domínios de pipeline e estrutura. Será que é OK se eu criar outro conjunto de dados de utility network na mesma instância - o novo terá domínios elétricos e de estrutura? Esses conjuntos de dados cobrirão geografias diferentes e terão referências espaciais diferentes. <\/P> <\/P> O que me preocupa são os domínios de estrutura. Haverá conflito de nomes para os dois conjuntos de classes de feição de estrutura?<\/P> <\/P> Qualquer dica será apreciada.<\/P> <\/P> Obrigado, Ed<\/P><\/BODY><\/HTML>

EdwardBlair · Answer

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.

Ed

RichardDumont · Answer

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.

PaulLeBlanc1 · Answer

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.