The ArcSDE administrative account in SQL Server

The ArcSDE administrative user account is responsible for the administration of the following:

• ArcSDE geodatabase system tables, triggers, and procedures
• The ArcSDE service
• Versions

The ArcSDE administrator owns all the ArcSDE geodatabase system files, directories, and tables. For this reason, the ArcSDE administrative account must be created before the geodatabase can be created. The database administrator (DBA) creates the ArcSDE administrator and grants this user the necessary permissions. This can be accomplished using the Post Installation wizard or manually in the Microsoft SQL Server instance.

The geodatabase administrative user in SQL Server can be either dbo or sde.

The dbo user is a special user in SQL Server; the user that created the database is considered dbo as are any users in the sysadmin system role. If you use a dbo ArcSDE geodatabase administrator, you must use the single spatial database model.

Tip:

You can use either a dbo or sde ArcSDE geodatabase administrator with the single spatial database model. However, If you use a multiple spatial database model (an older method of geodatabase creation in SQL Server), your ArcSDE administrator must be sde.

For more information on using a dbo ArcSDE administrator, see A comparison of geodatabase owners in SQL Server.

For information on the multiple database model for SQL Server, see The SQL Server multiple spatial database model.

Keep in mind that the ArcSDE administrative user is not the same as the DBA. Although conditions at your site may necessitate that the ArcSDE administrator have DBA-level permissions, this is not required for day-to-day operation of an ArcSDE geodatabase.

The ArcSDE administrative user and schema

It is recommended that the ArcSDE administrator and its schema only be used to manage and store ArcSDE system tables. You should create separate user schemas in which to store your ArcSDE data objects, such as feature classes and raster datasets. You should not store these objects in the ArcSDE administrator’s storage space, since you could possibly crash the ArcSDE service by filling up the ArcSDE administrator’s space. Following the practice of storing only system tables in the ArcSDE administrator's storage space simplifies the management of ArcSDE.

In SQL Server 2005 and later releases, users do not automatically have a schema with the same name as their user name. However, to use SQL Server with ArcSDE, your user names must have corresponding default schema names. This applies to the ArcSDE administrator user as well as nonadministrative users who create data.