Database versions and version policies

This page describes Cloud SQL's database version support policies.

Database versions supported by Cloud SQL

The database engines supported by Cloud SQL include multiple versions. The versions can vary in capabilities and in the types of issues that arise. While performing an upgrade can impact your users, providing up-to-date database features and important patches is also critical. Cloud SQL keeps your instances up-to-date with patches and minor version updates automatically.

Major and minor versions supported by Cloud SQL

Cloud SQL supports the following database versions.

The mainstream end date and the Microsoft extended support end dates follow the Microsoft SQL Server support lifecycle. These dates are different than the Cloud SQL extended support dates that apply to Cloud SQL for PostgreSQL and Cloud SQL for MySQL.

While Cloud SQL does charge for extended support for MySQL and PostgreSQL, Cloud SQL doesn't charge for extended support for Microsoft SQL Server.

Major versionMinor versionSupport start dateMainstream support
end date
Extended support
end date
SQL Server 2025 StandardCU2November 18, 2025January 6, 2031January 6, 2036
SQL Server 2025 EnterpriseCU2November 18, 2025January 6, 2031January 6, 2036
SQL Server 2025 ExpressCU2November 18, 2025January 6, 2031January 6, 2036
SQL Server 2022 StandardCU19June 26, 2023January 11, 2028January 11, 2033
SQL Server 2022 EnterpriseCU19June 26, 2023January 11, 2028January 11, 2033
SQL Server 2022 ExpressCU19June 26, 2023January 11, 2028January 11, 2033
SQL Server 2022 WebCU19June 26, 2023January 11, 2028January 11, 2033
SQL Server 2019 StandardCU32June 24, 2021February 28, 2025January 8, 2030
SQL Server 2019 EnterpriseCU32June 24, 2021February 28, 2025January 8, 2030
SQL Server 2019 ExpressCU32June 24, 2021February 28, 2025January 8, 2030
SQL Server 2019 WebCU32June 24, 2021February 28, 2025January 8, 2030
SQL Server 2017 Standard1CU31February 19, 2020October 11, 2022October 13, 2027
SQL Server 2017 Enterprise1CU31February 19, 2020October 11, 2022October 13, 2027
SQL Server 2017 Express1CU31February 19, 2020October 11, 2022October 13, 2027
SQL Server 2017 Web1CU31February 19, 2020October 11, 2022October 13, 2027

1: Beginning April 12, 2027, you won't be able to create new instances of Cloud SQL for SQL Server 2017. Starting on October 13, 2027, SQL Server 2017 will reach end of life (EOL) and Microsoft will stop releasing security updates. Cloud SQL for SQL Server will stop supporting SQL Server 2017 after this date.

Cloud SQL database version format

For SQL Server, the year provides the major version number and the minor version is the supported Cumulative Update (CU). For example, for SQL Server 2022 Enterprise CU11, 2022 Enterprise is the major version number and CU11 is the minor version number.

How to identify the database version of your Cloud SQL instance

You specify the database version when you create a Cloud SQL instance. If you don't specify a database version, then Cloud SQL uses the default database version.

You can check the database version of a single Cloud SQL instance or find instances by version across a Google Cloud project, folder, or organization by using the Google Cloud console or the gcloud CLI.

Console

For a single instance

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

    Go to Cloud SQL Instances

  2. To open the Overview page of an instance, click the instance name.
  3. In the Configuration card, view the Database version.

In a single project

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

    Go to Cloud SQL Instances

  2. In the Filter field, select Type. The database versions in your project are listed.
  3. Select a database version to filter the instances in your project.

In an organization, folder, or project

To view Cloud SQL instances and their database versions across an organization or folder in Database Center, make sure that you have the Database Center Viewer (roles/databasecenter.viewer) Identity and Access Management (IAM) role on that organization or folder. For more information, see Set up Database Center.

  1. In the Google Cloud console, go to the Database Center page.

    Go to Database Center

  2. In the project picker in the Google Cloud console menu bar, select your organization, folder, or Google Cloud project.
  3. Click All Resources, and then use the Products & versions filter to select the Cloud SQL versions that you want to inspect.
  4. Optional: To download the filtered fleet inventory to a CSV file, click CSV Export. For more information, see Filter resources and export fleet inventory information.

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.

In a single project

To list Cloud SQL instances and their database versions in a single project, use the gcloud sql instances list command:

gcloud sql instances list --project=PROJECT_ID

Replace PROJECT_ID with the ID of your Google Cloud project. To filter by engine or major version, add --filter="databaseVersion:VERSION_PREFIX*", where VERSION_PREFIX is an API enum prefix such as SQLSERVER or SQLSERVER_2022_ENTERPRISE.

In an organization, folder, or project

To list Cloud SQL instances across an organization or folder by using gcloud asset list, make sure that the Cloud Asset Inventory API is enabled on your quota project and that you have the Cloud Asset Viewer (roles/cloudasset.viewer) IAM role on the organization, folder, or project. For more information, see Roles and permissions.

gcloud asset list \
    --organization=ORGANIZATION_ID \
    --asset-types="sqladmin.googleapis.com/Instance" \
    --content-type=resource \
    --filter="resource.data.databaseVersion:VERSION_PREFIX*" \
    --format="table(
        resource.data.project,
        resource.data.name,
        resource.data.databaseVersion,
        resource.data.state,
        resource.data.settings.activationPolicy,
        resource.data.region
    )"

Replace the following:

  • ORGANIZATION_ID: the numeric ID of your organization. To query a folder or a single project instead, replace --organization=ORGANIZATION_ID with --folder=FOLDER_ID or --project=PROJECT_ID.
  • VERSION_PREFIX: the database engine or major version prefix in sqladmin.googleapis.com/Instance format: specify SQLSERVER to list all Cloud SQL for SQL Server instances, or specify SQLSERVER_MAJOR_VERSION with spaces replaced by underscores (for example, SQLSERVER_2019 for all 2019 editions or SQLSERVER_2022_ENTERPRISE for a specific edition). For supported API enum strings, see SqlDatabaseVersion.

The output includes both running instances (activationPolicy: ALWAYS) and stopped instances (activationPolicy: NEVER), along with the project ID, instance name, full database version, state, and region.

Minor version support

Cloud SQL supports new minor versions within three months of their general availability release by the database engine developer community. After Cloud SQL supports a new minor version, Cloud SQL provisions new instances on the new version automatically. During the next scheduled maintenance rollout, Cloud SQL upgrades existing instances to the new version.

Cloud SQL determines the target minor version for each database engine. When the target minor version is different from the minor version for a Cloud SQL instance, Cloud SQL upgrades that version during the next maintenance cycle. You can control the day and time when maintenance restarts occur by setting a maintenance window for your instance.