Skip To Content

Upgrade an enterprise geodatabase in SQL Server on Amazon Web Services

Once you upgrade ArcGIS Pro or ArcGIS Server on the instances in your ArcGIS Enterprise on Amazon Web Services (AWS) deployment, you can upgrade the enterprise geodatabases in Microsoft SQL Server. The steps to upgrade the geodatabase vary slightly depending on whether the geodatabase runs in a SQL Server database or Amazon Relational Database Service (RDS) for SQL Server instance.

Note:

If the geodatabase contains branch versioned data, additional postupgrade steps may be required. See How Upgrade Geodatabase works for instructions.

After you upgrade the geodatabase to the current release, ArcGIS Pro 2.2 and earlier clients and ArcGIS 10.6.1 and earlier clients can no longer connect to the geodatabase.

Upgrade an enterprise geodatabase in SQL Server

The following steps assume you created the geodatabase using ArcGIS Enterprise on Amazon Web Services tools, which create dbo-schema geodatabases in SQL Server.

Follow these steps to upgrade an enterprise geodatabase in a SQL Server instance on AWS:

  1. Create a full backup of each of the databases that contains an enterprise geodatabase in the SQL Server instance on AWS.
    1. Using the administrator login, connect to the Amazon Elastic Compute Cloud (EC2) instance where SQL Server is installed.
    2. Start Microsoft SQL Server Management Studio and sign in to it using Windows authentication.
    3. Create backups of each database that contains a geodatabase to be upgraded.
    4. Close Management Studio to ensure you disconnect from the databases.
  2. Stop any ArcGIS Server web services that access data in the geodatabase before you upgrade.

    There cannot be any users other than the administrator connected to the geodatabase when you upgrade, including service connections.

    1. Sign in to ArcGIS Server Manager for the ArcGIS Server site on AWS and stop all services that reference data in the geodatabase to be upgraded.
    2. Sign in to an EC2 instance in AWS that has an installation of ArcGIS Pro, and confirm there are no other connections to the geodatabase.

      Ensure that the ArcGIS Pro EC2 instance is in the same region as the SQL Server EC2 instance.

  3. While still in ArcGIS Pro, run the Upgrade Geodatabase geoprocessing tool.

    See Upgrade an enterprise geodatabase in SQL Server in the ArcGIS Pro help for more information.

  4. If you have other enterprise geodatabases in SQL Server, repeat the previous two steps to upgrade them.
  5. Restart the ArcGIS Server web services.

Upgrade a geodatabase in Amazon RDS for SQL Server

Follow these steps to upgrade a geodatabase in Amazon RDS for SQL Server:

  1. Sign in to AWS Management Console and create a snapshot of the RDS for SQL Server instance.
  2. Connect to the RDS for SQL Server instance from SQL Server Management Studio and add the sde user to the db_owner role in the database.
  3. Close SQL Server Management Studio and AWS Management Console.
  4. Ensure that no users other than the administrator are connected to the geodatabase when you upgrade. You must stop any ArcGIS Server web services that access data in the geodatabase before you upgrade.
    1. Sign in to ArcGIS Server Manager for the ArcGIS Server site on AWS and stop all services that reference data in the geodatabase to be upgraded.
    2. Sign in to an EC2 instance in AWS that has an installation of ArcGIS Pro, and confirm there are no other connections to the geodatabase.

      You must connect as the sde user.

      Ensure the ArcGIS Pro EC2 instance is in the same region as the Amazon RDS for SQL Server instance.

  5. While still in ArcGIS Pro, run the Upgrade Geodatabase geoprocessing tool.

    See Upgrade an enterprise geodatabase in SQL Server in the ArcGIS Pro help for more information.

  6. If you have other enterprise geodatabases in Amazon RDS for SQL Server, repeat the previous steps to upgrade them.
  7. Restart the ArcGIS Server web services.
  8. Connect to the RDS for SQL Server instance (or instances) from SQL Server Management Studio and remove the sde user from the db_owner database role.