To move the contents of one geodatabase in Microsoft SQL Server to another, you can do one of the following:
- Create a second geodatabase and use ArcGIS tools to move the data.
- Move the entire database using SQL Server tools.
Move data to another geodatabase using ArcGIS
To move your data to a different geodatabase, you must first create a second geodatabase. Next, connect to both geodatabases from an ArcGIS client and move the data from the old geodatabase to the new geodatabase using one of the following methods:
- Copy and paste
- Export tools
- Export and import XML workspace documents
Remember that data is loaded to the schema of the database user who connects to the geodatabase. Also remember that database names must be unique per SQL Server instance. Therefore, if you create the second geodatabase on the same SQL Server instance, you must provide a different name for the second geodatabase.
Move a database using SQL Server tools
SQL Server provides several options to move databases, including detaching the database file from the SQL Server instance and attaching it to a new instance, creating a backup of the database and restoring it to a new SQL Server instance, or using 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 restore 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.
For details and instructions on using SQL Server tools to move databases, consult your SQL Server documentation.