AGIS data administrator needs to migrate the enterprise geodatabase to another server and wants to have the following changes: • New enterprise…

The required changes—a new geodatabase name and altering the repository owner from SDE to DBO—are fundamental configuration settings established during the geodatabase's initial creation. The only workflow that accommodates these specific changes is to create a new, empty enterprise geodatabase on the target server. During this process, the administrator can define the new name and use the "Enable Enterprise Geodatabase" tool to specify 'DBO' as the geodatabase administrator, which in turn creates the repository tables in the DBO schema. After the new geodatabase is correctly configured, data from the old geodatabase can be migrated into it using methods like XML workspace documents or copy/paste operations.

A. Restore a database backup: This method creates an exact replica of the source database, preserving the original geodatabase name and the 'SDE' schema owner. It does not allow for reconfiguration during the migration.

C. Migrate Storage geoprocessing tool: This tool is designed to change the underlying data storage format (e.g., from SDEBINARY to Geometry) for individual tables within an existing geodatabase, not to migrate the entire geodatabase or change its core properties.

---

1. Esri ArcGIS Pro Documentation, "Enable an enterprise geodatabase in SQL Server": This document outlines the process of creating a geodatabase. It explicitly states, "If the geodatabase administrator is the dbo user, the geodatabase system tables, views, functions, and stored procedures are created in the dbo schema." This confirms that specifying the owner is part of the creation/enablement process.

Source: Esri ArcGIS Pro 3.2 Documentation, "Data management" > "Geodatabases" > "Administer" > "Enable an enterprise geodatabase in SQL Server".

2. Esri ArcGIS Pro Documentation, "Geodatabase migration options": This page discusses different strategies for moving a geodatabase. It implicitly supports the "create new and load data" approach for scenarios where the target configuration (like schema or name) must be different from the source, as opposed to a simple backup/restore for identical moves.

Source: Esri ArcGIS Pro 3.2 Documentation, "Data management" > "Geodatabases" > "Administer" > "Geodatabase migration options".

3. Esri ArcGIS Pro Tool Reference, "Migrate Storage (Data Management)": The official tool documentation clearly defines its limited scope. The summary states: "Migrates the storage of a geodatabase table or feature class from one storage type to another." This confirms it is not a tool for migrating an entire geodatabase to a new server or changing its owner.

Source: Esri ArcGIS Pro 3.2 Documentation, "Tool Reference" > "Data Management toolbox" > "Geodatabase Administration toolset" > "Migrate Storage".