Preparing to upgrade a geodatabase in SQL Server
When you upgrade any enterprise system, including a geodatabase, plan ahead. Test the new version on a development or test server to ensure that it works with all your client applications.
When you have determined that the new system works the way you expected, schedule the upgrade; be sure the necessary staff are available to perform the upgrade and that they have the permissions necessary to complete their assigned tasks.
Be aware of the following:
- Upgrades from beta versions of the software are not supported.
- You can upgrade directly from a 9.3.x, 10, 10.1, or 10.2 geodatabase to a 10.2.2 geodatabase if your database is at a supported release. There is no geodatabase upgrade from version 10.2.1 to 10.2.2; all changes made between those releases were implemented in the ArcGIS client applications.
- If your geodatabase is at release 9.2 or earlier, you must first upgrade to a supported geodatabase release then upgrade to 10.2.2.
- Once a geodatabase has been upgraded, previous versions of ArcGIS may not be able to connect since some older versions of ArcGIS cannot read newer versions of the geodatabase. Releases prior to ArcGIS 10 will not be able to connect to a 10.2.x geodatabase. ArcGIS 10 clients will be able to connect to the 10.2.x geodatabase.
- There is no formal mechanism to downgrade a geodatabase to a previous version. If after upgrading to a newer version you want to move back to an older version of the geodatabase, you must restore the old database from backup.
- When a geodatabase in SQL Server is upgraded to ArcGIS 10.1 or later releases, newly created feature classes will use the SQL Server geometry storage type by default. If you want new feature classes to use a different type of geometry storage by default, use the sdedbtune command to change the GEOMETRY_STORAGE parameter value under the DEFAULTS keyword. (The sdedbtune command can be installed using the ArcSDE application server installation wizard.)
You must also complete the following steps before you upgrade your geodatabase in SQL Server:
Check the ArcGIS Resource Center to be sure that your database, operating system, and other components meet at least the minimum system requirements.
Your database must be at a supported release and your hardware must meet at least the minimum system requirements before you upgrade your geodatabase.
- Create a backup of the database.
- If you use an ArcSDE service for connections and have customized any of the files in the etc directory of SDEHOME, make a copy of these files.
If you do not have the Full-Text Indexing component installed in the database, install it.
Some columns in the geodatabase system tables require this component.
- Remove any custom functionality you may have added to the ArcSDE geodatabase system tables outside ArcGIS, such as triggers, participation in SQL Server replication, or additional indexes. The upgrade procedure cannot be aware of customizations you make to the system tables. If such customizations prevent the alteration of a system table, the upgrade will fail.
Make sure that the login you use to upgrade the geodatabase has the correct privileges.
If the geodatabase is stored in the dbo schema, the geodatabase administrator (dbo) automatically has the privileges necessary to upgrade. For geodatabases stored in the sde schema, if it is a single-spatial-database model geodatabase and the database is not named sde, the login you use must either be sysadmin or in the db_owner role. If you are using a multispatial-database model geodatabase (or a single-spatial-database named sde), you must log in as sysadmin to upgrade.Note:
Do not add the sde user to sysadmin.
- Install the current release of an ArcGIS client (ArcGIS for DesktopStandard or Advanced, ArcGIS Engine with the Geodatabase Update extension, or ArcGIS for Server Enterprise Standard or Advanced) on a computer that can directly connect to the geodatabase to perform the upgrade.
Make sure the SQL Server Native Client is installed on the computer where the ArcGIS client is installed.
This is required because you must connect directly to SQL Server from ArcGIS to upgrade the geodatabase. If you are installing the SQL Server Native Client on a 64-bit operating system, use the 64-bit SQL Server Native Client executable.
Make sure there are no users connected to the geodatabase you are upgrading.
You can see a list of the users who are currently connected to your geodatabase by opening the Connected Users tab of the Geodatabase Administration dialog box in ArcGIS for Desktop.
If you are using an ArcSDE service, do the following:
- Stop the ArcSDE service using the Windows Services interface.
If you are upgrading to a new, full release of the ArcSDE application server (such as from 9.3.1 or 10 to 10.1), uninstall the old release of ArcSDE, and delete the old service when prompted to do so.
If you are applying a service pack or patch, do not perform this step.
- Obtain the ArcSDE Application Server installation from the Esri Customer Care portal.
If you are unsure of the database compatibility level of your SQL Server database, check the database properties from Microsoft SQL Server Management Studio. If your database compatibility level is 80, you must update your database compatibility level. See SQL Server documentation for instructions.
The geodatabase is now ready to be upgraded. You can use the Upgrade Geodatabase tool in ArcGIS for Desktop or a Python script run on the ArcGIS client computer.
If you use an ArcSDE service for connections, install the ArcSDE application server after you upgrade your geodatabase.