Other methods for moving a geodatabase in SQL Server

There are several options within Microsoft SQL Server to move a database. They include using detach and attach, backup and restore, or the Copy Database wizard.

No matter which of the methods you use to move your SQL Server database, you cannot rename the database. When you are restoring a database, for example, you are given the opportunity to restore it with a different name. Don't do this with a geodatabase; you won't be able to connect to it.

All object names in the geodatabase system tables are fully qualified with the database name. In addition, many stored procedures use a three-part naming syntax in their code, which follows the format <database>.<owner>.<object>. If the database name changes, you will not be able to execute these procedures.

If you are using a multiple spatial database instance—that is, the SDE database and other databases are all part of a single geodatabase—you must move the entire geodatabase. Every database that is referenced in the ArcSDE and geodatabase tables must be accounted for, or the target data may be inoperable.

Use detach and attach

The easiest way to move a geodatabase stored in a SQL Server database is to detach the database from the source server and attach it to the destination server. Keep in mind that

Restore backup of another database

Another option for moving a SQL Server database is to do a full backup of the database and restore the backup file to your destination server. Keep the following in mind:

For details on restoring backups of ArcSDE for SQL Server databases, consult your SQL Server DBMS documentation.

Copy Database wizard (Management Studio)

NoteNote:

Applies to geodatabases created with an ArcGIS Server Enterprise license only

SQL Server Management Studio (SQL Server 2005 and 2008) provides a Copy Database wizard you can use to move databases. Some things to consider when using the Copy Database wizard are as follows:


8/19/2013