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

Was it a mistake to create enterprise geodatabases with my OS account?

PaulHuffman

I have five enterprise geodatabases in ArcServer 10.6.1 and SQL Server that I created with the Create Enterprise Geodatabase tool from my domain login, so the Database Admin account is my OS account on my local domain. But when I retire in a couple months, how can I pass this Databasee Admin authority to my successor admin? Did I screw up? Because right now I can't figure out the best way to hand this off. Will I need to leave my account on the domain so the new admin will have to add my domain login to her PC and have to switch to my user account to use ArcCatalog to do the admin on these geodatabases, like add users, create roles, add users to roles? Or can the new admin use SSMS to manage database users? But I can't remember SSMS can use my admin credentials from a PC logged into the domain with someone else's credentials.

But at least I have headless DB accounts for the data owner and the geodatabase administrator account.

Find more posts tagged with

Accepted answers

All comments

PaulHuffman

I got an error trying to use the Create Database User tool in Desktop 10.6.1. [Microsoft][ODBC Driver 13 for SQL Server] [SQL Server] Cannot use the special principal 'sa'. Is it not recommended to create a user "sa" to be the database owner with sysadmin priviledges? Or should I use SSMS to create this user "sa"?

ConnorFriese

The "sa" account is recognized as DBO because that user has the "sysadmin" fixed server role.

Since it is a headless account it would probably be easier to set this user as the database owner.

DBO versus the database owner is a common confusion and something specific to SQL Server. This documents may provide some insight into the differences.

https://stackoverflow.com/questions/2731787/what-is-the-difference-between-db-owner-and-the-user-that-owns-the-database

https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/sql/server-and-database-roles-in-sql-server

PaulHuffman

I took a look at my settings with SSMS. I wanted to create a new DB account to take over as the database owner, but I found there already is a user dbo with the login name of my OS login. So it is potentially confusing to admins after me, because it looks like dbo is the expected practice. Maybe I'll name the new DB user account "DBOwner" to give System Administrator privileges.

My class textbook from "Deploying and Maintaining a Multiuser Geodatabase" used "sa" as the account name for the database owner. Maybe I'll go with that.

ConnorFriese

Paul Huffman‌

The most important thing noted is that you still have headless account for the data owner and geodatabase administrator.

This will allow you to to do many geoprocessing functions.

Now in regards to running a tool like Create Database User, that does require someone with System Administrator privileges.

Since you are using SQL Server, a user can be granted the server role "sysadmin".

https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/sql/server-and-database-roles-in-sql-server

If a user is part of that "sysadmin" role then they have System Administrator privileges and will be able to execute tools that requires those privileges.

Once a user has the "sysadmin" role then they will be known as DBO.

http://desktop.arcgis.com/en/arcmap/latest/manage-data/gdbs-in-sql-server/comparison-geodatabase-owners-sqlserver.htm

Now, if you right-click on the database (in SSMS), go to properties, and click the General tab then you will get a window like this.

Here you will see the actual owner of the database will still be your OS user.

This really shouldn't have any impact when it comes to doing ESRI workflows.

However, I found some Microsoft documentation that may address how to change this.

https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-changedbowner-transact-sql?view=sql-server-2017

https://blog.arvixe.com/change-database-owner-with-sql-server-management-studio/

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.