Every type of geodatabase requires at least some amount of management to configure and maintain it. The following sections summarize the management tasks you perform based on the type of geodatabase you are using.
File geodatabase management
There are a few management tasks involved in the use of a file geodatabase. Some of these tasks, such as compacting a geodatabase or re-creating a spatial grid index, help maintain performance. Others, such as compressing vector data or creating a licensed file geodatabase, are optional.
Enterprise geodatabase management
Enterprise geodatabases are stored inside a database. Geodatabases are supported in the following relational database management systems:
- IBM Db2
- Microsoft SQL Server
- Oracle
- PostgreSQL
- SAP HANA
Typically, a large number of users access enterprise geodatabases. As a result, administration is required to make sure the geodatabase is configured properly, people can access the data they need, and the database runs smoothly.
You can perform some geodatabase administration tasks using ArcGIS. In many cases, administration tasks are slightly different from one database management system to another. Therefore, there is a section in the help specific to each supported database management system. Be sure to read the topics pertaining to the one you are using.
Key tasks for the administration of an enterprise geodatabase include the following:
Install software and create a geodatabase
You need to install both the database management system software and ArcGIS software, create a database, and enable geodatabase functionality in the database.
Obtain the database management system installation from a third-party vendor. If you're using PostgreSQL, you can download a supported version from My Esri.
Once your ArcGIS client and database management system software are installed and configured, use either the Create Enterprise Geodatabase (Oracle, PostgreSQL, and SQL Server only) or Enable Enterprise Geodatabase geoprocessing tool or a Python script to create a geodatabase.
Manage user access
To control access to the geodatabase, create or add user accounts to the database. To simplify user administration, you will likely create groups or roles and add users to them. Use database tools to accomplish this or, for some database platforms, you can use geoprocessing tools.
- The Create Role geoprocessing tool creates database groups or roles in Oracle, PostgreSQL, and SQL Server.
- The Create Database User geoprocessing tool creates users that have privileges to create data in the database. When you run this tool, you can also assign the user to a database role. You can use it with Oracle, PostgreSQL, SAP HANA, or SQL Server databases.
Once users have been added to the database, grant permissions to them, individually or in groups, to allow them to perform their work in the geodatabase. These include Data Definition Language (DDL) privileges to create, alter, or drop objects in the database. Individual data owners can grant Data Manipulation Language (DML) privileges to other users or groups to allow them to select, insert, update, or delete records in their tables and feature classes. DML privileges can be granted through wizards in ArcGIS Desktop or using geoprocessing tools. See Grant and revoke dataset privileges for information on how to manage DML privileges on the tables and feature classes you own in the geodatabase. For information on privileges needed for different types of users, see the topic specific to your database management system:
Connect to the geodatabase
Users connect to the geodatabase from ArcGIS client applications to create and work with data. To connect to most database management systems, you must install a database client on the ArcGIS client computer. Once that is installed, you or the users need to create a connection file (.sde) to access the geodatabase.
See the topic specific to your database management system for information on connecting to an enterprise geodatabase:
- Connect to Db2 from ArcGIS
- Connect to Oracle from ArcGIS
- Connect to PostgreSQL from ArcGIS
- Connect to SAP HANA from ArcGIS
- Connect to SQL Server from ArcGIS
Once you've created a connection file, you can rename it. Note that this only renames the .sde file, not the geodatabase or the database in which it is stored. To rename the connection file, right-click the database connection in the Project pane, click Rename, type a new connection name, and press Enter. The database connection must be part of your project for you to rename it.
Maintain the geodatabase
As people add data to the geodatabase, the geodatabase must be maintained so the data is available to all authorized users when needed and without any depreciation in performance.
To ensure the data is not lost, the database administrator must perform regular backups and have a recovery plan in place and tested.
When large amounts of data are added to or updated in enterprise geodatabases, update database statistics and indexes to be sure the database's optimizer can efficiently query the data. The geodatabase administrator can update statistics and indexes on system tables using the Analyze Datasets and Rebuild Indexes geoprocessing tools, respectively. Data owners can use these tools to update statistics and indexes on their own data tables. Database administrators can perform these tasks directly in the database.
If your geodatabase uses traditional versioning, the geodatabase administrator must regularly compress the geodatabase to maintain performance levels. Use the Compress geoprocessing tool or a Python script to accomplish this.
Upgrade the geodatabase
When a new release of ArcGIS is available, your organization may want to move to that release to take advantage of new functionality and fixes. As an administrator, you should set up a test servers on which you install the new ArcGIS software and upgrade a copy of your production geodatabase. Tests should then be run to ensure the new version works as you expected. Note that moving to a newer geodatabase version may require you to upgrade the database management system as well.
Once testing is complete, you can upgrade the production software and geodatabases. See the topic for your database management system for geodatabase upgrade instructions: