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; } } }

Parcel Fabric Data Owner - DB acct vs OS acct

AdamCrateau

According to the help docs for Parcel Fabrics in an eGDB, the data owner of the PF or Utility Network cannot be an OS authenticated user.

Does anyone know why this is, and will Esri change this in the future? My DBA has security concerns with DB accounts in SQL Server

Encuentra más publicaciones etiquetadas con

Enterprise geodatabase

Geodatabase Administration

Accepted answers

MMBR

Hello @ACrateau the database user name, the database schema name and the database login name must have the same name, this is one of the reasons why you cannot use an OS authenticated user as the data owner, and the contrary, the best practice is never to use an OS authenticated user as data owner, but a database user. You can learn to create/configure the enterprise geodatabase with best practices from my database guide books and database templates scripts in the link below.
community.esri.com - Mapping and Charting Solutions (MCS) Enterprise Databases Best Practices

Read the "Production Mapping" guide book series. You can use the same best practices for "Parcel Fabric Geodatabases".

All comments

MarlonAmaya

Hi @ACrateau

Regarding UN owner and whether or not it will be changed (updated), submit on the UN community that is tracked by UN team.

https://community.esri.com/t5/arcgis-utility-network/ct-p/arcgis-utility-network

Marlon

MMBR

Read the "Production Mapping" guide book series. You can use the same best practices for "Parcel Fabric Geodatabases".

AdamCrateau

Thank you Marcelo. In our test case, the user name, database schema and database login all match, for example, "Domain\user". We use an OS authenticated user in SQL Server as a data owner for other simple feature classes and topologies without issue. I'm not completely clear on why this approach will not work for advanced feature types like Parcel Fabric.

It's clear that we'll need to use a DB user for now.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

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