Note:This topic was updated for 9.3.1.
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 and PostgreSQL, users do not automatically have a schema with the same name as their user name. However, to use SQL Server or PostgreSQL with ArcSDE, your user names must
have corresponding default schema names. This applies to the ArcSDE administrator user as well as nonadministrative users.
NOTE: When adding administrative or any other types of users to SQL Server Express, a matching schema is automatically created because the ArcGIS interface creates the matching schema for you. See the following section for information on administrative users in SQL Server Express.
The administrative users for database servers (SQL Server Express instances used to store ArcSDE geodatabases licensed through ArcGIS Desktop, ArcGIS Engine, or ArcGIS Server Workgroup) are different. Since administration for these databases and the SQL Server Express instances in which they are created takes place solely through ArcCatalog or ArcObjects, there are two different types of administrative users: server administrators and geodatabase administrators.
On a database server, permission to work with the SQL Server Express instance and the geodatabase objects is controlled by users and groups assigned to roles. The user identifies who you are, and a role defines the operations you will be able to perform. The server administrator is a Windows-authenticated user assigned to the server administrator role (the sysadmin fixed server role in the database). Members of the sysadmin server role are automatically dbo.
The server administrator is sort of like the DBA and ArcSDE administrator rolled into one. This user can add other users to the database server and control user permissions, create and delete geodatabases, detach and attach databases, and back up and restore databases. In addition, this user can perform ArcSDE administrative tasks in the geodatabase such as compressing the geodatabase.
Because the server administrator creates the geodatabases on the database server, this user owns the ArcSDE geodatabase system tables.
The other type of administrative user—a geodatabase administrator—is a Windows-authenticated user assigned to the geodatabase database owner role (db_owner). This user can perform administrative tasks such as administering other users' geodatabase permissions, making a backup of the geodatabase, and compressing the geodatabase. Geodatabase administrators cannot administer the database server or other geodatabases for which they have not been given administrator privileges.
For additional information on users in database servers, see Adding and removing users or groups for ArcSDE database servers
and Administering user permissions for ArcSDE database servers