Upgrade the database major version in-place

MySQL | PostgreSQL | SQL Server

This page describes how to upgrade the database major version by upgrading your Cloud SQL instance in-place rather than by migrating data.

Introduction

Database software providers periodically release new major versions that contain new features, performance improvements, and security enhancements. Cloud SQL takes in new versions after they're released. After Cloud SQL offers support for a new major version, you can upgrade your instances to keep your database updated.

You can upgrade the database version of an instance in-place or by migrating data. In-place upgrades are a simpler way to upgrade your instance's major version. You don't need to migrate data or change application connection strings. With in-place upgrades, you can retain the name, IP address, and other settings of your current instance after the upgrade. In-place upgrades don't require you to move data files and can be completed faster. In some cases, the downtime is shorter than what migrating your data entails.

The Cloud SQL for SQL Server in-place upgrade operation uses the SQL Server upgrade in-place utility.

Plan a major version upgrade

Choose a target major version.
gcloud

For information about installing and getting started with the gcloud CLI, see Install the gcloud CLI. For information about starting Cloud Shell, see Use Cloud Shell.

To check the database versions that you can target for an in-place upgrade on your instance, do the following:
1. Run the following command.
2. In the output of the command, locate the section that is labeled upgradableDatabaseVersions.
3. Each subsection returns a database version that is available for upgrade. In each subsection, review the following fields.
REST v1

To check which target database versions are available for a major version in-place upgrade, use the instances.get method of the Cloud SQL Admin API.

Before using any of the request data, make the following replacements:
- INSTANCE_NAME: The instance name.
HTTP method and URL:
GET https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)

Note: The following command assumes that you have logged in to the gcloud CLI with your user account by running gcloud init or gcloud auth login , or by using Cloud Shell, which automatically logs you into the gcloud CLI . You can check the currently active account by running gcloud auth list.

Execute the following command:
curl -X GET \
-H "Authorization: Bearer $(gcloud auth print-access-token)" \
"https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME"
PowerShell (Windows)

Note: The following command assumes that you have logged in to the gcloud CLI with your user account by running gcloud init or gcloud auth login . You can check the currently active account by running gcloud auth list.

Execute the following command:
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
-Method GET `
-Headers $headers `
-Uri "https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
You should receive a JSON response similar to the following:
upgradableDatabaseVersions: { major_version: "SQLSERVER_2022_STANDARD" name: "SQLSERVER_2022_STANDARD" display_name: "SQL Server 2022 Standard" }
REST v1beta4

To check which target database versions are available for major version in-place upgrade of an instance, use the instances.get method of the Cloud SQL Admin API.

Before using any of the request data, make the following replacements:
- INSTANCE_NAME: The instance name.
HTTP method and URL:
GET https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME
To send your request, expand one of these options:
curl (Linux, macOS, or Cloud Shell)

Note: The following command assumes that you have logged in to the gcloud CLI with your user account by running gcloud init or gcloud auth login , or by using Cloud Shell, which automatically logs you into the gcloud CLI . You can check the currently active account by running gcloud auth list.

Execute the following command:
curl -X GET \
-H "Authorization: Bearer $(gcloud auth print-access-token)" \
"https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME"
PowerShell (Windows)

Note: The following command assumes that you have logged in to the gcloud CLI with your user account by running gcloud init or gcloud auth login . You can check the currently active account by running gcloud auth list.

Execute the following command:
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }

Invoke-WebRequest `
-Method GET `
-Headers $headers `
-Uri "https://sqladmin.googleapis.com/sql/v1beta4/projects/PROJECT_ID/instances/INSTANCE_NAME" | Select-Object -Expand Content
You should receive a JSON response similar to the following:
upgradableDatabaseVersions: { major_version: "SQLSERVER_2022_STANDARD" name: "SQLSERVER_2022_STANDARD" display_name: "SQL Server 2022 Standard" }
For the complete list of the database versions that Cloud SQL supports, see Database versions and version policies.
Consider the features offered in each database major version and address incompatibilities.

See SQL Server discontinued features and breaking changes.

New major versions introduce incompatible changes that might require you to modify the application code, the schema, or the database settings. Before you can upgrade your database instance, review the release notes of your target major version to determine the incompatibilities that you must address.

Note: While upgrading your major version, you can also upgrade your SQL Server edition. For example, you can upgrade from SQL Server 2017 Standard to SQL Server 2019 Enterprise. If you decide to upgrade your edition, be sure to review Cloud SQL for SQL Server license pricing.
Test the upgrade with a dry run.

Perform a dry run of the end-to-end upgrade process in a test environment before you upgrade the production database. You can clone your instance to create an identical copy of the data on which to test the upgrade process.

In addition to validating that the upgrade completes successfully, run tests to ensure that the application behaves as expected on the upgraded database.

Note: Ensure that you have enough disk space before running a major version upgrade. If you haven't enabled automatic storage increases, take note of the disk storage used by the upgraded dry run instance. This helps you determine whether you need to increase the storage capacity for the production instance before upgrading.
Decide on a time to upgrade.

Upgrading requires the instance to become unavailable for a period of time. Plan to upgrade during a time period when database activity is low.

Upgrade the database major version in-place

When you initiate an upgrade operation, Cloud SQL first checks the configuration of your instance to ensure that it's compatible for an upgrade. After verifying your configuration, Cloud SQL makes your instance unavailable, makes a pre-upgrade backup, performs the upgrade, makes your instance available, and makes a post-upgrade backup.

Console

In the Google Cloud console, go to the Cloud SQL Instances page.

Go to Cloud SQL Instances
To open the Overview page of an instance, click the instance name.
Click Edit.
In the Instance info section, click the Upgrade button and confirm that you want to go to the upgrade page.
On the Choose a database version page, click the Database version for upgrade list and select one of the available database major versions.
Click Continue.
In the Instance ID box, enter the name of the instance and then click the Start upgrade button.

The operation takes several minutes to complete.

Verify that the upgraded database major version appears below the instance name on the instance Overview page.

gcloud

Start the upgrade.

Use the gcloud sql instances patch command with the --database-version flag.

Before running the command, replace the following:
- INSTANCE_NAME: The name of the instance.
- DATABASE_VERSION: The enum for the database major version, which must be later than the current version. Specify a database version for a major version that is available as an upgrade target for the instance. You can obtain this enum as the first step of Plan for upgrade. If you need a complete list of database version enums, then see SqlDatabaseEnums.
```
gcloud sql instances patch INSTANCE_NAME \
--database-version=DATABASE_VERSION
```
Major version upgrades take several minutes to complete. You might see a message indicating that the operation is taking longer than expected. You can either ignore this message or run the gcloud sql operations wait command to dismiss the message.
Get the upgrade operation name.

Use the gcloud sql operations list command with the --instance flag.

Before running the command, replace the INSTANCE_NAME variable with the name of the instance.
```
gcloud sql operations list --instance=INSTANCE_NAME
```
Monitor the status of the upgrade.

Use the gcloud sql operations describe command.

Before running the command, replace the OPERATION variable with the upgrade operation name retrieved in the previous step.
```
gcloud sql operations describe OPERATION
```

REST v1

Start the in-place upgrade.

Use a PATCH request with the instances:patch method.

Before using any of the request data, replace these variables:
- PROJECT_ID: The ID of the project.
- INSTANCE_NAME: The name of the instance.
HTTP method and URL:
```
PATCH https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/instances/INSTANCE_NAME
```
Request JSON body:
```
{
  "databaseVersion": DATABASE_VERSION
}
```
Replace DATABASE_VERSION with the enum for the database major version, which must be later than the current version. Specify a database version for a major version that is available as an upgrade target for the instance. You can obtain this enum as the first step of Plan for upgrade. If you need a full list of database version enums, then see SqlDatabaseVersion.
Get the upgrade operation name.

Use a GET request with the operations.list method after replacing PROJECT_ID with the ID of the project.

HTTP method and URL:
```
GET https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operations
```
Monitor the status of the upgrade.

Use a GET request with the operations.get method after replacing the following variables:
- PROJECT_ID: The ID of the project.
- OPERATION_NAME: The upgrade operation name retrieved in the previous step.
HTTP method and URL:
```
GET https://sqladmin.googleapis.com/v1/projects/PROJECT_ID/operation/OPERATION_NAME
```

Terraform

To update the version of the database, use a Terraform resource and the Terraform provider for Google Cloud, version 4.34.0 or later.

resource "google_sql_database_instance" "instance" {
  name             = "sqlserver-instance"
  region           = "us-central1"
  database_version = "SQLSERVER_2019_STANDARD"
  root_password    = "INSERT-PASSWORD-HERE"
  settings {
    tier = "db-custom-2-7680"
  }
  # set `deletion_protection` to true, will ensure that one cannot accidentally delete this instance by
  # use of Terraform whereas `deletion_protection_enabled` flag protects this instance at the GCP level.
  deletion_protection = false
}

Apply the changes

To apply your Terraform configuration in a Google Cloud project, complete the steps in the following sections.

Prepare Cloud Shell

Launch Cloud Shell.
Set the default Google Cloud project where you want to apply your Terraform configurations.

You only need to run this command once per project, and you can run it in any directory.
```
export GOOGLE_CLOUD_PROJECT=PROJECT_ID
```
Environment variables are overridden if you set explicit values in the Terraform configuration file.

Prepare the directory

Each Terraform configuration file must have its own directory (also called a root module).

In Cloud Shell, create a directory and a new file within that directory. The filename must have the .tf extension—for example main.tf. In this tutorial, the file is referred to as main.tf.
```
mkdir DIRECTORY && cd DIRECTORY && touch main.tf
```
If you are following a tutorial, you can copy the sample code in each section or step.

Copy the sample code into the newly created main.tf.

Optionally, copy the code from GitHub. This is recommended when the Terraform snippet is part of an end-to-end solution.
Review and modify the sample parameters to apply to your environment.
Save your changes.
Initialize Terraform. You only need to do this once per directory.
```
terraform init
```
Optionally, to use the latest Google provider version, include the -upgrade option:
```
terraform init -upgrade
```

Apply the changes

Review the configuration and verify that the resources that Terraform is going to create or update match your expectations:
```
terraform plan
```
Make corrections to the configuration as necessary.
Apply the Terraform configuration by running the following command and entering yes at the prompt:
```
terraform apply
```
Wait until Terraform displays the "Apply complete!" message.
Open your Google Cloud project to view the results. In the Google Cloud console, navigate to your resources in the UI to make sure that Terraform has created or updated them.

Delete the changes

To delete your changes, do the following:

To disable deletion protection, in your Terraform configuration file set the deletion_protection argument to false.
```
deletion_protection =  "false"
```
Apply the updated Terraform configuration by running the following command and entering yes at the prompt:
```
terraform apply
```

Remove resources previously applied with your Terraform configuration by running the following command and entering yes at the prompt:
```
terraform destroy
```

When you place an in-place upgrade request, Cloud SQL first performs a pre-upgrade check. If Cloud SQL determines that your instance isn't ready for an upgrade, then your upgrade request fails with a message suggesting how you can address the issue. See also Troubleshoot a major version upgrade.

Automatic upgrade backups

When you perform a major version upgrade, Cloud SQL automatically makes two on-demand backups, called upgrade backups:

The first upgrade backup is the pre-upgrade backup, which is made immediately before starting the upgrade. You can use this backup to restore your database instance to its state on the previous version.
The second upgrade backup is the post-upgrade backup, which is made immediately after new writes are allowed to the upgraded database instance.

When you view your list of backups, the upgrade backups are listed with type On-demand. Upgrade backups are labeled so that you can identify them quickly. For example, if you're upgrading from SQL Server Enterprise 2017 to SQL Server Enterprise 2019, your pre-upgrade backup is labeled as Pre-upgrade backup, SQLSERVER_2017_ENTERPRISE to SQLSERVER_2019_ENTERPRISE. and your post-upgrade backup is labeled as Post-upgrade backup, SQLSERVER_2019_ENTERPRISE from SQLSERVER_2017_ENTERPRISE.

As with other on-demand backups, upgrade backups persist until you delete them or delete the instance.

Upgrade the database compatibility level

The database compatibility level determines how the database behaves with respect to the application it serves. The database compatibility level setting ensures backward compatibility with earlier versions of SQL Server and relates to Transact-SQL and Query Optimizer changes. When a SQL Server instance database version is upgraded, the compatibility levels of existing databases are preserved, such that the application can continue to operate on the more recent version of SQL Server. Upgrading the compatibility level helps you benefit from new features, query processing improvements, and other changes.

After you've upgraded an instance's database engine version, when the application that the database serves is ready, upgrade the database compatibility level for each database in the instance. When the compatibility level is set to the latest, databases are upgraded with the latest features and improved performance.

To upgrade the database compatibility level, perform the following steps:

Identify the current compatibility level of your database.

For example, for SQL Server 2017, the default compatibility level is 140. To check the current compatibility level for your database, run the following command in Transact-SQL, after replacing DATABASE_NAME

with the name of the database on your SQL Server instance.
```
USE DATABASE_NAME
GO
SELECT compatibility_level
FROM sys.databases WHERE name = 'DATABASE_NAME'
```
Determine the target compatibility level.

Identify the default compatibility level designation for your upgraded database version to determine the target compatibility level for your database. For example, for SQL Server 2022, the default compatibility level is 160. See the table mapping new versions of SQL Server with compatibility levels.
Assess the differences between your current and target compatibility levels.

Before you upgrade the compatibility level, study the differences in system behavior between your current compatibility level and your target compatibility level. See the complete list of the differences between compatibility levels.
Collect a baseline of workload data.

Before upgrading the compatibility level, collect a baseline of workload data by using SQL Server Query Store, so that you can later identify and address regressed queries. You use Query Store to capture queries and plans for a typical business cycle to establish a performance baseline. For a guided workflow, use the Query Tuning Assistant feature in SQL Server Management Studio.
Upgrade the compatibility level.

To change the compatibility level for the database, run the following command in Transact-SQL, after replacing DATABASE_NAME

with the name of the database on your SQL Server instance and TARGET_COMPATIBILITY_LEVEL with the target compatibility level.
```
ALTER DATABASE DATABASE_NAME
SET COMPATIBILITY_LEVEL = TARGET_COMPATIBILITY_LEVEL;
GO
```
Collect upgraded workload data.

Collect upgraded workload data using Query Store for comparison and regression detection.
Address regressed queries.

For the most part, Query Optimizer changes in upgraded compatibility levels improve performance. However, from time to time, certain queries might regress in performance. Query Store's Regressed Queries feature helps you identify the queries that have regressed and lets you force the last known good query plan. SQL Server also offers automatic plan correction, which can automatically switch to the last known good plan in the event of a query regression.

Complete the major version upgrade

After upgrading your primary instance, perform acceptance tests to ensure that the upgraded system performs as expected.

Troubleshoot a major version upgrade

Cloud SQL returns an error message if you attempt an invalid upgrade command, for example, if your instance contains invalid database flags for the new version.

If your upgrade request fails, check the syntax of your upgrade request. If the request has a valid structure, try looking into the following suggestions.

View upgrade logs

If any issues occur with a valid upgrade request, Cloud SQL publishes error logs to projects/PROJECT_ID/logs/cloudsql.googleapis.com%2Fsqlserver.err. Each log entry contains a label with the instance identifier to help you identify the instance with the upgrade error. Look for such upgrade errors and resolve them.

To view error logs, follow these steps:

In the Google Cloud console, go to the Cloud SQL Instances page.

Go to Cloud SQL Instances
To open the Overview page of an instance, click the instance name.
In the Operations and logs pane of the instance Overview page, click the View SQL Server error logs link.

The Logs Explorer page opens.
View logs as follows:
- To list all error logs in a project, select the log name in the Log name log filter.
For more information on query filters, see Advanced queries.
- To filter the upgrade error logs for a single instance, enter the following query in the Search all fields box, after replacing DATABASE_ID
with the project ID followed by the instance name in this format: project_id:instance_name.
```
resource.type="cloudsql_database"
resource.labels.database_id="DATABASE_ID"
logName : "projects/PROJECT_ID/logs/cloudsql.googleapis.com%2Fsqlserver.err"
```
For example, to filter the upgrade error logs by an instance named shopping-db running in the project buylots, use the following query filter:
```
 resource.type="cloudsql_database"
 resource.labels.database_id="buylots:shopping-db"
 logName : "projects/buylots/logs/cloudsql.googleapis.com%2Fsqlserver.err"
```

Restore to the previous major version

If your upgraded database system doesn't perform as expected, you might need to restore your instance to the previous version. You do so by restoring your pre-upgrade backup to a Cloud SQL recovery instance, which is a new instance running the pre-upgrade version.

To restore to the previous version, perform the following steps:

Identify your pre-upgrade backup.

See Automatic upgrade backups.
Create a recovery instance.

Create a new Cloud SQL instance using the major version that Cloud SQL was running when the pre-upgrade backup was made. Set the same flags and instance settings that the original instance uses.
Restore your pre-upgrade backup.

Restore your pre-upgrade backup to the recovery instance. This might take several minutes to complete.
Add your read replicas.

If you were using read replicas, add them individually.
Connect your application.

Having recovered your database system, update your application with details about the recovery instance and its read replicas. You can resume serving traffic on the pre-upgrade version of your database.

Limitations

This section lists limitations for an in-place major version upgrade.

You can't perform an in-place major version upgrade on an external replica.

FAQs

The following questions might come up when upgrading the database major version.

Is my instance unavailable during an upgrade?: Yes. Your instance remains unavailable for a period of time while Cloud SQL performs the upgrade.

How long does an upgrade take?

Upgrading a single instance typically takes less than 10 minutes. If your instance configuration uses a small number of vCPUs or memory, then your upgrade might take more time.

If your instance hosts too many databases or tables, or your databases are very large, then the upgrade might take hours or even time out because the upgrade time corresponds to the number of objects in your databases. If you have multiple instances that need to be upgraded, then your total upgrade time increases proportionately.

Can I monitor each step in my upgrade process?: While Cloud SQL allows you to monitor whether an upgrade operation is still in progress, you are unable to track the individual steps in each upgrade.

Can I cancel my upgrade after I've started it?: No, you can't cancel an upgrade once it has started. If your upgrade fails, Cloud SQL automatically recovers your instance on the previous version.

What happens to my settings during an upgrade?

When you perform an in-place major version upgrade, Cloud SQL retains your database settings, including your instance name, IP address, explicitly configured flag values, and user data. However, the default value of the system variables might change.

To learn more, see Configure database flags. If a certain flag or value is no longer supported in your target version, then Cloud SQL automatically removes the flag during the upgrade.

What's next

Learn about options for connecting to an instance.
Learn about importing and exporting data.
Learn more about setting database flags.

Upgrade the database major version in-place

Introduction

Plan a major version upgrade

gcloud

REST v1

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

REST v1beta4

curl (Linux, macOS, or Cloud Shell)

PowerShell (Windows)

Upgrade the database major version in-place

Console

gcloud

REST v1

Terraform

Apply the changes

Prepare Cloud Shell

Prepare the directory

Apply the changes

Delete the changes

Automatic upgrade backups

Upgrade the database compatibility level

Complete the major version upgrade

Troubleshoot a major version upgrade

View upgrade logs

Restore to the previous major version

Limitations

FAQs

What's next