@SamSzotkowski "Branch versioned data must not be owned by the SDE or DBO users."
This means the data, e.g. featureclasses, tables, feature datasets, geodatabase domains, etc. must not be owned by the sde user which is the arcsde repository owner nor by DBO.
In SQL Server there are 2 options to create the ArcSDE repository, 1) dbo owned or 2) sde user owned.
Create a geodatabase in SQL Server—ArcGIS Pro | Documentation
I tell all my customers to not use DBO, it does not provide the level of security for your data that is necessary, and instead always use the ArcSDE Repository with the sde user owner.
Now, that you created the ArcSDE Repository with the sde user owner, next you shall not use the sde user to load the data, the sde user is the geodatabase repository owner and must be used only for geodatabase administration tasks, then you must create a data owner users to load the data.
Example:
SQL Server Geodatabase Name: waterdb
ArcSDE Geodatabase Repository Owner: sde
Data Owner User Water Data Model: water
For more best practices please visit my community.esri.com blog below. There you will find the ArcGIS Pro database guide books for SQL Server, and you can also download my database template scripts for SQL Server to assist to setup the SQL Server Geodatabase. You can use the Production Mapping database guidebooks, the best practices can be applied to any industry.
Mapping and Charting Solutions (MCS) Enterprise Databases Best Practices
I hope this helps.
| Marcelo Marques | Principal Product Engineer | Esri |
| Cloud & Database Administrator | OCP - Oracle Certified Professional |
I work with Enterprise Geodatabases since 1997.
“ I do not fear computers. I fear the lack of them." Isaac Isimov