Cloud SQL release notes

Cloud SQL for MySQL 9.7 is generally available (GA).

For more information about the differences between MySQL 9.7 and previous versions, review the MySQL 9.7 Release Notes.

By default, if you specify MySQL 9.7 as the version when you create a Cloud SQL instance (either primary or replica) using the gcloud CLI, the Google Cloud console, or the REST API, then the Cloud SQL edition is Cloud SQL Enterprise Plus edition.

This release introduces support for key MySQL 9.7 capabilities, including:

• Vector search: support for the community-standard vector storage format combined with advanced approximate nearest neighbor (ANN) vector indexing in Cloud SQL.
• Hypergraph optimizer: an alternative join-planning framework designed for complex, multi-table queries. You can enable the hypergraph optimizer using an optimizer switch.
• JSON Duality Views: a feature that bridges relational SQL and hierarchical JSON document models to interact with the same underlying data.
• Upgrade and migration paths: support for in-place major version upgrade from Cloud SQL for MySQL 8.4 and migrations from MySQL 8.4 using the Database Migration Service (DMS).

Flag updates for MySQL 9.7

Additionally, this release introduces several database flag changes.

For more information about MySQL database flags, see Configure database flags.

Newly created instances configured with high availability (HA) now have Knowledge Catalog (formerly Dataplex Universal Catalog) enabled by default.

Cloud SQL for PostgreSQL instances running on PostgreSQL version 14.0 or later send updates and metadata to Knowledge Catalog in near real-time.

You can either verify enablement or disable the feature using the Google Cloud console.

For more information, see Near real-time.

Newly created instances configured with high availability (HA) now have Knowledge Catalog (formerly Dataplex Universal Catalog) enabled by default.

Cloud SQL for SQL Server instances send updates and metadata to Knowledge Catalog to help support data discovery.

You can either verify enablement or disable the feature using the Google Cloud console.

For more information, see Manage your Cloud SQL resources using Knowledge Catalog.

Performance capture for Cloud SQL for MySQL is now generally available (GA). Performance capture lets you take a point-in-time snapshot of your database and operating system metrics automatically and route them to Cloud Logging for root-cause analysis.

With the GA release, you can configure custom thresholds that end long-running transactions automatically before they slow down your database. In addition, the GA release includes six additional performance capture triggers:

• High CPU utilization
• High memory usage
• High temporary files usage
• History list length
• Semaphore waits
• Transaction lock waits

For more information, see Cloud SQL performance capture overview.

DNS automation is now generally available (GA) on Cloud SQL instances where Private Service Connect is enabled.

You can use DNS automation to provision and manage per-instance DNS records automatically. On Enterprise Plus edition instances where DNS automation is enabled, you can also enable a global write endpoint DNS that automatically resolves to your current primary instance.

Cloud SQL for MySQL supports resource groups. MySQL resource groups let you manage resource allocation for different workloads on your Cloud SQL for MySQL instance. By using resource groups, you can prevent less important workloads from consuming excessive CPU or memory resources.

To use MySQL resource groups, you must have maintenance version MYSQL_VERSION.R20260320.00_20 or later installed on your instance.

For more information, see Manage CPU allocation with MySQL resource groups.

DNS automation is now generally available (GA) on Cloud SQL instances where Private Service Connect is enabled.

You can use DNS automation to provision and manage per-instance DNS records automatically. On Enterprise Plus edition instances where DNS automation is enabled, you can also enable a global write endpoint DNS that automatically resolves to your current primary instance.

DNS automation is now generally available (GA) on Cloud SQL instances where Private Service Connect is enabled.

You can use DNS automation to provision and manage per-instance DNS records automatically. On Enterprise Plus edition instances where DNS automation is enabled, you can also enable a global write endpoint DNS that automatically resolves to your current primary instance.

You can change the backup plan for your Cloud SQL enhanced backups without first removing the existing plan. For more information, see Change your instance's associated backup plan.

You can change the backup plan for your Cloud SQL enhanced backups without first removing the existing plan. For more information, see Change your instance's associated backup plan.

You can change the backup plan for your Cloud SQL enhanced backups without first removing the existing plan. For more information, see Change your instance's associated backup plan.

Starting on August 1, 2026, when you create or clone a Cloud SQL instance enabled with Private Service Connect, or when you enable Private Service Connect for an existing instance, then connection reconciliation behavior is enabled by default and can't be disabled.

When you remove a project from the list of allowed projects, all existing Private Service Connect connections from the removed project are immediately closed (reconciled). This means that applications using Private Service Connect endpoints in those removed projects can't continue to connect to the Cloud SQL instance using those endpoints.

For more information, see Allowed Private Service Connect projects.

QueryData adds support for parameterized secure views (PSVs) to help secure applications that use natural language queries. For more information, see Secure and control access to application data.

This feature is in Preview.

Starting on August 1, 2026, when you create or clone a Cloud SQL instance enabled with Private Service Connect, or when you enable Private Service Connect for an existing instance, then connection reconciliation behavior is enabled by default and can't be disabled.

When you remove a project from the list of allowed projects, all existing Private Service Connect connections from the removed project are immediately closed (reconciled). This means that applications using Private Service Connect endpoints in those removed projects can't continue to connect to the Cloud SQL instance using those endpoints.

For more information, see Allowed Private Service Connect projects.

Starting on August 1, 2026, when you create or clone a Cloud SQL instance enabled with Private Service Connect, or when you enable Private Service Connect for an existing instance, then connection reconciliation behavior is enabled by default and can't be disabled.

When you remove a project from the list of allowed projects, all existing Private Service Connect connections from the removed project are immediately closed (reconciled). This means that applications using Private Service Connect endpoints in those removed projects can't continue to connect to the Cloud SQL instance using those endpoints.

For more information, see Allowed Private Service Connect projects.

Cloud SQL for SQL Server now supports executing SQL statements using the Cloud SQL Data API.

Cloud SQL for MySQL now supports significantly faster re-encryption of instances and replicas protected by customer-managed encryption keys (CMEKs), and re-encryption now completes with zero downtime. The steps to re-encrypt your instances and replicas are unchanged, but the operation now re-encrypts the underlying disks in-place, without creating re-encryption backups.

For more information, see Re-encrypt an existing CMEK-enabled instance or replica.

Cloud SQL for PostgreSQL now supports significantly faster re-encryption of instances and replicas protected by customer-managed encryption keys (CMEKs), and re-encryption now completes with zero downtime. The steps to re-encrypt your instances and replicas are unchanged, but the operation now re-encrypts the underlying disks in-place, without creating re-encryption backups.

For more information, see Re-encrypt an existing CMEK-enabled instance or replica.

Cloud SQL for SQL Server now supports significantly faster re-encryption of instances and replicas protected by customer-managed encryption keys (CMEKs), and re-encryption now completes with zero downtime. The steps to re-encrypt your instances and replicas are unchanged, but the operation now re-encrypts the underlying disks in-place, without creating re-encryption backups.

For more information, see Re-encrypt an existing CMEK-enabled instance or replica.

Cloud SQL for PostgreSQL now supports logical replication using failover slot which you can use with advanced disaster recovery (DR) switchover and replica failover operations to ensure business continuity.

For more information, see Advanced disaster recovery (DR) with logical failover slot.

Cloud SQL for PostgreSQL now supports authentication via Secret Manager when executing SQL statements using the Data API (executeSql). You can store your database password in a regional secret in Secret Manager and pass the secret version resource name in your API request.

For more information, see Execute SQL statements on a Cloud SQL instance.

Cloud SQL for MySQL 8.4.8 is upgraded to MySQL 8.4.10. For more information, see the MySQL 8.4.10 Release Notes and Cloud SQL database versions.

You can now create and query parameterized secure views in Cloud SQL for MySQL. Parameterized secure views let you create MySQL views in your MySQL database that reference session variables for managing data access. By using a parameterized secure view, you can create a single view that is flexible enough to accommodate multiple queries across a predefined range of data without being required to create multiple static view definitions for different users.

To use parameterized secure views, you're required to have Cloud SQL for MySQL 8.0.43 or later and maintenance version R20260320.00_20 or later installed on your instance.

For more information, see Parameterized secure views in Cloud SQL. This feature is in Preview.

MySQL 8.0.45 is now the default minor version for Cloud SQL for MySQL 8.0.

For more information about minor version support in Cloud SQL for MySQL, see MySQL 8.0.

You can now assess the upgrade readiness of your Cloud SQL for MySQL instances before a major version upgrade by running a precheck. This precheck analyzes your instance for version incompatibilities and lists any issues that need to be fixed prior to your upgrade. For more information, see Assess upgrade readiness for your instance.

This feature is in Preview.

Cloud SQL now supports Private Service Connect outbound connectivity on the following additional types of instances:

• Read replica instances.

• Instances that use advanced disaster recovery features such as switchover and failover operations.

For more information about Private Service Connect outbound connectivity see About Private Service Connect.

Cloud SQL now supports Private Service Connect outbound connectivity on the following additional types of instances:

• Read replica instances.

• Instances that use advanced disaster recovery features such as switchover and failover operations.

For more information about Private Service Connect outbound connectivity see About Private Service Connect.

Cloud SQL now supports Private Service Connect outbound connectivity on the following additional types of instances:

• Read replica instances.

• Instances that use advanced disaster recovery features such as switchover and failover operations.

• Primary instances that have replicas.

For more information about Private Service Connect outbound connectivity see About Private Service Connect.

Customer-managed encryption key (CMEK) support for Cloud SQL enhanced backups is generally available. You can protect your CMEK-enabled Cloud SQL instances using Google Cloud Backup and DR Service.

For more information, see Choose your backup option.

Customer-managed encryption key (CMEK) support for Cloud SQL enhanced backups is generally available. You can protect your CMEK-enabled Cloud SQL instances using Google Cloud Backup and DR Service.

For more information, see Choose your backup option.

When you migrate from Percona XtraBackup physical file to Cloud SQL for MySQL, you can now specify multiple data files in the innodb_data_file_path parameter of your external server configuration. Also, you are no longer required to use the default name for your data files.

Cloud SQL for MySQL now supports multiple system tablespace files, allowing system tablespace size to grow larger than 16TB.

Cloud SQL for MySQL now supports minor version 8.0.46. To upgrade your existing instance to the new minor version, see Upgrade the database minor version.

Cloud SQL is integrated with Google AI Studio to help you build full-stack applications that use a Cloud SQL for PostgreSQL developer edition instance as the database. You can enter natural language prompts in the Google AI Studio to build applications backed by Cloud SQL and add features such as authentication, search, and persistent data storage.

For more information, see Build vibe-coded applications using Google AI Studio and Cloud SQL.

This feature is generally available (GA).

The rollout of the following Cloud SQL for PostgreSQL minor version and extension upgrades is complete:

Minor versions

• 14.22 is upgraded to 14.23.
• 15.17 is upgraded to 15.18.
• 16.13 is upgraded to 16.14.
• 17.9 is upgraded to 17.10.
• 18.3 is upgraded to 18.4.

The new maintenance version is [PostgreSQL version].R20260319.07_04. To apply the new maintenance version, see Perform self-service maintenance.

QueryData adds support for parameterized secure views (PSVs) to help secure applications that use natural language queries. For more information, see Secure and control access to application data.

This feature is in Preview.

You can publish a Cloud SQL for MySQL conversational analytics agent in Gemini Enterprise. This feature is in Preview.

You can publish a Cloud SQL for PostgreSQL conversational analytics agent in Gemini Enterprise. This feature is in Preview.

You can now create and query parameterized secure views in Cloud SQL for PostgreSQL.

Parameterized secure views let you use PostgreSQL views with more granular access control over your data. While you can issue a GRANT statement to control whether a user can query a PostgreSQL view, a GRANT statement doesn't let you control the data that the view returns based on the user who is making the query.

To gain this level of control, use parameterized secure views. You can define parameters such as a user ID or region within the view. When your application queries the view, a user can provide values for these parameters, which customizes the query results. Using parameterized secure views lets you enforce "least privilege" access to help ensure that your users interact only with the data that is relevant and authorized to them.

This feature is in Preview.

Cloud SQL Enterprise Plus arm-based C4A machine types, powered by Google's Axion processors, are now available in 8 additional regions:

• asia-northeast1: Tokyo, Japan
• australia-southeast2: Melbourne, Australia
• europe-north1: Finland
• northamerica-northeast1: Montréal, Québec, Canada
• northamerica-northeast2: Toronto, Ontario, Canada
• southamerica-west1: Santiago, Chile
• us-east5: Columbus, Ohio, USA
• us-west2: Los Angeles, California, USA

For information about C4A machine types, see The C4A machine series.

Cloud SQL for MySQL managed buffer pool is now generally available (GA). Managed buffer pool helps you avoid out-of-memory events (OOMs) on your Cloud SQL instance by reducing innodb_buffer_pool_size when memory usage is high.

Cloud SQL Enterprise Plus Arm-based C4A machine types, powered by Google's Axion processors, are available in 8 additional regions:

• asia-northeast1: Tokyo, Japan
• australia-southeast2: Melbourne, Australia
• europe-north1: Finland
• northamerica-northeast1: Montréal, Québec, Canada
• northamerica-northeast2: Toronto, Ontario, Canada
• southamerica-west1: Santiago, Chile
• us-east5: Columbus, Ohio, USA
• us-west2: Los Angeles, California, USA

For information about C4A machine types, see The C4A machine series.

The command for upgrading Cloud SQL instances to the new network architecture has been re-enabled.

For more information, see Upgrade an instance to the new network architecture.

The command for upgrading Cloud SQL instances to the new network architecture has been re-enabled.

For more information, see Upgrade an instance to the new network architecture.

The command for upgrading Cloud SQL instances to the new network architecture has been re-enabled.

For more information, see Upgrade an instance to the new network architecture.

Cloud SQL for MySQL now supports regional endpoints for the Cloud SQL Admin API. This feature lets you direct your API calls to a region-specific endpoint. Using a regional endpoint enhances data locality and helps meet strict compliance expectations.

This feature includes: * Regional boundary restrictions: Cloud SQL regional endpoints enforce strict matching. The region of the target API resource must match the region of the endpoint exactly. Otherwise, the request is rejected with a 4xx error. * Restricted API visibility: When you use a regional endpoint, the Instance.List API only returns resources located within that specific region.

For more information, see Cloud SQL regional endpoints.

This feature is in Preview.

Cloud SQL for PostgreSQL now supports regional endpoints for the Cloud SQL Admin API. This feature lets you direct your API calls to a region-specific endpoint. Using a regional endpoint enhances data locality and helps meet strict compliance expectations.

This feature includes: * Regional boundary restrictions: Cloud SQL regional endpoints enforce strict matching. The region of the target API resource must match the region of the endpoint exactly. Otherwise, the request is rejected with a 4xx error. * Restricted API visibility: When you use a regional endpoint, the Instance.List API only returns resources located within that specific region.

For more information, see Cloud SQL regional endpoints.

This feature is in Preview.

Cloud SQL for SQL Server now supports regional endpoints for the Cloud SQL Admin API. This feature lets you direct your API calls to a region-specific endpoint. Using a regional endpoint enhances data locality and helps meet strict compliance expectations.

This feature includes: * Regional boundary restrictions: Cloud SQL regional endpoints enforce strict matching. The region of the target API resource must match the region of the endpoint exactly. Otherwise, the request is rejected with a 4xx error. * Restricted API visibility: When you use a regional endpoint, the Instance.List API only returns resources located within that specific region.

For more information, see Cloud SQL regional endpoints.

This feature is in Preview.

Cloud SQL for SQL Server now supports PolyBase (GA).

With PolyBase, your Cloud SQL for SQL Server instance uses Transact-SQL (T-SQL) commands to directly query data stored in external data sources as if the data is stored in local tables. You don't need to install separate client connection software.

For more information, see About PolyBase.

Cloud SQL has made the following enhancements to expand the list of eligible Cloud SQL Enterprise Plus edition instances that support planned operations with near-zero downtime.

• Instances with connector enforcement enabled are eligible for planned operations with near-zero downtime.
• Instances that use private services access with a non-RFC 1918 IP address are eligible for planned operations with near-zero downtime.

Cloud SQL has made the following enhancements to expand the list of eligible Cloud SQL Enterprise Plus edition instances that support planned operations with near-zero downtime.

• Instances with connector enforcement enabled are eligible for planned operations with near-zero downtime.
• Instances that use private services access with a non-RFC 1918 IP address are eligible for planned operations with near-zero downtime.

If a specific active query is blocked or running much longer than expected, it can block other dependent queries. Cloud SQL for SQL Server offers an optional feature that lets you view and terminate blocking queries.

For more information, see Blocked active queries (Preview).

The cloudsql_session_read_only session parameter provides a robust, non-circumventable mechanism in Cloud SQL for PostgreSQL for preventing data modification during a session. You can use this flag to either make a session temporarily read-only, or make a session permanently, irreversibly read-only.

For more information, see Create a read-only session in Cloud SQL for PostgreSQL.

Removed a query insights limitation for Cloud SQL Enterprise Plus edition and Cloud SQL Enterprise edition instances that use PostgreSQL 18.

Instances using PostgreSQL maintenance version 20260319.00_RC02 or any later version now store application tags when using query insights even if a query has comment tags before the start of a SQL statement.

Database Migration Service quick-start migrations are now integrated into Cloud SQL for PostgreSQL to provide a lightweight, continuous migration flow. This feature automates setup for sources with private IPs in a VPC network, including Cloud SQL for PostgreSQL instances and self-managed databases on Compute Engine.

For more information, see Quick-start migrations overview in the Database Migration Service documentation. This feature is in Preview.

You can use the Database Insights remote MCP server to analyze Cloud SQL for MySQL's performance and system metrics. This feature is in GA.

You can use the Database Insights remote MCP server to analyze Cloud SQL for PostgreSQL's performance and system metrics. This feature is in GA.

You can use the Database Insights remote MCP server to analyze Cloud SQL for SQL Server's performance and system metrics. This feature is in GA.

Newly created Cloud SQL instances are integrating with Knowledge Catalog (formerly Dataplex Universal Catalog) for data discovery. Instances on MySQL version 8.0 or later will have updates sent to Knowledge Catalog in near real-time. As part of this automatic enablement, we will send metadata to Knowledge Catalog. You can verify if your instance is enabled for integration with Knowledge Catalog by looking at the configuration pane in the Knowledge Catalog console. If you don't want your instance to be integrated with Knowledge Catalog, you can turn off this feature.

For more information, see Near real-time.

Newly created Cloud SQL instances are integrating with Knowledge Catalog (formerly Dataplex Universal Catalog) for data discovery. Instances on PostgreSQL version 14.0 or later will have updates sent to Knowledge Catalog in near real-time. As part of this automatic enablement, we will send metadata to Knowledge Catalog. You can verify if your instance is enabled for integration with Knowledge Catalog by looking at the configuration pane in the Knowledge Catalog console. If you don't want your instance to be integrated with Knowledge Catalog, you can turn off this feature.

For more information, see Near real-time.

Newly created Cloud SQL instances are integrating with Knowledge Catalog (formerly Dataplex Universal Catalog) for data discovery. As part of this automatic enablement, we will send metadata to Knowledge Catalog. You can verify if your instance is enabled for integration with Knowledge Catalog by looking at the configuration pane in the Knowledge Catalog console. If you don't want your instance to be integrated with Knowledge Catalog, you can turn off this feature.

For more information, see Create a new instance with Knowledge Catalog integration enabled.

You can now integrate Cloud SQL for SQL Server with Vertex AI and third-party models (Preview).

By integrating your Cloud SQL for SQL Server instance with Vertex AI, you can generate vector embeddings from models hosted in Vertex AI directly from your Cloud SQL instance.

Cloud SQL for SQL Server supports model endpoints from the following sources:

• Vertex AI
• Hugging Face
• OpenAI

For more information, see Integrate Cloud SQL for SQL Server with Vertex AI.

The Cloud SQL remote MCP server is generally available (GA). The Cloud SQL remote MCP server lets you interact easily with Cloud SQL instances from LLMs, AI applications, and AI-enabled development platforms.

You can use DNS automation on Cloud SQL instances where Private Service Connect is enabled to provision and manage per-instance DNS records automatically. On Enterprise Plus edition instances where DNS automation is enabled, you can also enable a global write endpoint DNS that automatically resolves to your current primary instance.

This feature is in Preview.

The Cloud SQL remote MCP server is generally available (GA). The Cloud SQL remote MCP server lets you interact easily with Cloud SQL instances from LLMs, AI applications, and AI-enabled development platforms.

You can use DNS automation on Cloud SQL instances where Private Service Connect is enabled to provision and manage per-instance DNS records automatically. On Enterprise Plus edition instances where DNS automation is enabled, you can also enable a global write endpoint DNS that automatically resolves to your current primary instance.

This feature is in Preview.

You can use DNS automation on Cloud SQL instances where Private Service Connect is enabled to provision and manage per-instance DNS records automatically. On Enterprise Plus edition instances where DNS automation is enabled, you can also enable a global write endpoint DNS that automatically resolves to your current primary instance.

This feature is in Preview.

The Cloud SQL remote MCP server is generally available (GA). The Cloud SQL remote MCP server lets you interact easily with Cloud SQL instances from LLMs, AI applications, and AI-enabled development platforms.

As of April 10, 2026, you can create, run, and edit Gemini Cloud Assist investigations only if you have a Premium Support contract. You can use Gemini Cloud Assist investigations to monitor and troubleshoot your Cloud SQL instance with AI assistance.

If you ran an investigation prior to April 10, 2026, then the results of the investigation continue to be available to you in the Google Cloud console.

As of April 10, 2026, you can create, run, and edit Gemini Cloud Assist investigations only if you have a Premium Support contract. You can use Gemini Cloud Assist investigations to monitor and troubleshoot your Cloud SQL instance with AI assistance.

If you ran an investigation prior to April 10, 2026, then the results of the investigation continue to be available to you in the Google Cloud console.

As of April 10, 2026, you can create, run, and edit Gemini Cloud Assist investigations only if you have a Premium Support contract. You can use Gemini Cloud Assist investigations to monitor and troubleshoot your Cloud SQL instance with AI assistance.

If you ran an investigation prior to April 10, 2026, then the results of the investigation continue to be available to you in the Google Cloud console.

The QueryData tool lets you to query the data in your database using conversational language and build data agents. For more information, see QueryData tool overview. This feature is available in (Preview).

The preview release increases the accuracy of SQL generation with value search queries which match values and their context within a database. Value search queries trigger automatically.

If the storage capacity of a Cloud SQL instance is larger than your application needs, then you can manually reduce, or shrink, your storage capacity to a smaller size.

Depending on underlying disk size, storage shrink operations might incur considerable downtime. If your instance requires limited downtime, rather than using storage shrink capabilities, we recommend migrating your data to a new, smaller instance using Database Migration Service.

For more information, see About storage shrink.

If the storage capacity of a Cloud SQL instance is larger than your application needs, then you can manually reduce, or shrink, your storage capacity to a smaller size.

Depending on underlying disk size, storage shrink operations might incur considerable downtime. If your instance requires limited downtime, rather than using storage shrink capabilities, we recommend migrating your data to a new, smaller instance using Database Migration Service.

For more information, see About storage shrink.

The QueryData tool lets you to query the data in your database using conversational language and build data agents. For more information, see QueryData tool overview. This feature is available in (Preview).

The preview release increases the accuracy of SQL generation with value search queries which match values and their context within a database. Value search queries trigger automatically.

If the storage capacity of a Cloud SQL instance is larger than your application needs, then you can manually reduce, or shrink, your storage capacity to a smaller size.

Depending on underlying disk size, storage shrink operations might incur considerable downtime. If your instance requires limited downtime, rather than using storage shrink capabilities, we recommend migrating your data to a new, smaller instance using Database Migration Service.

For more information, see About storage shrink.

Cloud SQL for SQL Server now supports SQL Server 2025 (GA):

• SQL Server 2025 Standard
• SQL Server 2025 Enterprise
• SQL Server 2025 Express

For more information, see Database versions and version policies and Choose a machine series.

Cloud SQL for SQL Server integration with Microsoft Entra ID (GA) provides centralized identity and access management (IAM) for your databases using your existing Microsoft Entra ID tenant.

Cloud SQL for SQL server read pools are now generally available and provide operational simplicity and scaling for your read workloads.

Read pools provide a single endpoint in front of up to seven read pool nodes and automatically load balance traffic.

You can scale your read pool in several ways:

• Scale in or out: scale load balancing capacity horizontally by modifying the number of read pool nodes in the read pool. Each read pool supports between 1 and 7 read pool nodes.

• Scale up or down: scale load balancing capacity vertically by modifying the machine type associated with a read pool node. Once defined, configuration is uniformly applied across each read pool node in the read pool.

For more information, see About read pools.

You can now migrate a subset of databases from an external server to a destination Cloud SQL for MySQL instance.

For more information, see Configure Cloud SQL and the external server for replication.

Cloud SQL for MySQL now offers conversational analytics, which lets users query their operational data using natural language. This feature is powered by the Conversational Analytics API, which can help you translate complex human dialog into precise database queries to provide actionable insights. This feature is in Preview. For more information, see Conversational analytics for Cloud SQL for MySQL overview.

Cloud SQL for PostgreSQL now offers conversational analytics, which lets users query their operational data using natural language. This feature is powered by the Conversational Analytics API, which can help you translate complex human dialog into precise database queries to provide actionable insights. This feature is in Preview. For more information, see Conversational analytics for Cloud SQL for PostgreSQL overview.

Vector assist (Preview) is temporarily disabled for all Cloud SQL for PostgreSQL instances.

MySQL 8.0.44 is now the default minor version for Cloud SQL for MySQL 8.0.

For more information about minor version support in Cloud SQL for MySQL, see MySQL 8.0.

Cloud SQL for MySQL now supports minor version 8.0.45. To upgrade your existing instance to the new minor version, see Upgrade the database minor version.

Multi-region backup vaults for Cloud SQL enhanced backups are generally available (GA).

This feature lets you store your backup data in multi-region storage locations, providing higher availability and protection against regional outages.

For more information, see Enhanced backups.

Cloud SQL supports cross-project PITR operations for instances protected by backup and DR (GA).

This feature lets you restore a Cloud SQL instance to a project other than the project where either the source instance or the backup vault is located.

For more information, see Perform a cross-project PITR.

You can now cancel an in-place major version upgrade operation during the main upgrade phase, when the upgrade is actually being performed.

For more information, see Cancel the major version upgrade.

Multi-region backup vaults for Cloud SQL enhanced backups are generally available (GA).

This feature lets you store your backup data in multi-region storage locations, providing higher availability and protection against regional outages.

For more information, see Enhanced backups.

Cloud SQL supports cross-project PITR operations for instances protected by backup and DR (GA).

This feature lets you restore a Cloud SQL instance to a project other than the project where either the source instance or the backup vault is located.

For more information, see Perform a cross-project PITR.

Cloud SQL supports cross-project PITR operations for instances protected by backup and DR (GA).

This feature lets you restore a Cloud SQL instance to a project other than the project where either the source instance or the backup vault is located.

For more information, see Perform a cross-project PITR.

Point-in-time recovery (PITR) default enablement behavior has changed:

• PITR is now enabled by default when you create a Cloud SQL Enterprise edition instance in the Google Cloud console.
• PITR is enabled by default when you create a Cloud SQL Enterprise Plus edition instance, regardless of the method used.

For more information, see Configure point-in-time recovery (PITR).

Multi-region backup vaults for Cloud SQL enhanced backups are generally available (GA).

This feature lets you store your backup data in multi-region storage locations, providing higher availability and protection against regional outages.

For more information, see Enhanced backups.

You can now enable automatic server certificate rotation for your Cloud SQL instance. This feature is specifically designed for instances utilizing the Certificate Authority Service (CAS). Automatic server certificate rotation helps you maintain high security standards while removing the operational burden of manual rotation.

For more information about enabling automatic server certificate rotation for your instance, see Enable automatic server certificate rotation.

You can now enable automatic server certificate rotation for your Cloud SQL instance. This feature is specifically designed for instances utilizing the Certificate Authority Service (CAS). Automatic server certificate rotation helps you maintain high security standards while removing the operational burden of manual rotation.

For more information about enabling automatic server certificate rotation for your instance, see Enable automatic server certificate rotation.

You can now enable automatic server certificate rotation for your Cloud SQL instance. This feature is specifically designed for instances utilizing the Certificate Authority Service (CAS). Automatic server certificate rotation helps you maintain high security standards while removing the operational burden of manual rotation.

For more information about enabling automatic server certificate rotation for your instance, see Enable automatic server certificate rotation.

You can now execute SQL statements using the Cloud SQL Data API for administrative queries.

You can now execute SQL statements using the Cloud SQL Data API for administrative queries.

Cloud SQL for MySQL 8.4.7 is upgraded to MySQL 8.4.8. For more information, see the MySQL 8.4.8 Release Notes.

It now takes less time to create a Cloud SQL instance when point-in-time recovery (PITR) is enabled, as it is by default in the Google Cloud console. During instance creation, PITR now initially uses an instant snapshot instead of a standard backup. and then later converts the snapshot to a standard backup in the background to support restore operations.

It now takes less time to create a Cloud SQL instance when point-in-time recovery (PITR) is enabled, as it is by default in the Google Cloud console. During instance creation, PITR now initially uses an instant snapshot instead of a standard backup. and then later converts the snapshot to a standard backup in the background to support restore operations.

Gemini Cloud Assist investigation capabilities are now supported in Cloud SQL for MySQL (Preview).

For more information, see Troubleshoot slow queries with AI assistance.

Gemini Cloud Assist investigation capabilities are now supported in Cloud SQL for PostgreSQL (Preview).

For more information, see Troubleshoot slow queries with AI assistance.

Gemini Cloud Assist investigation capabilities are now supported in Cloud SQL for SQL Server (Preview).

For more information, see Troubleshoot slow queries with AI assistance.

Cloud SQL now provides brute-force detection and protection for your Cloud SQL instances. This helps protect your instances from brute-force access attempts by identifying the source and mitigating the risk caused by these attempts. For more information, see Use brute-force protection.

After March 17, 2026, when you enable the Cloud SQL Admin API (sqladmin.googleapis.com), the Cloud SQL remote MCP server is enabled automatically.

The Cloud SQL remote MCP server is in Preview.

Control of MCP use with organization policies is deprecated. After March 17, 2026, organization policies that use the gcp.managed.allowedMCPServices constraint won't work, and you can control MCP use with IAM deny policies. For more information about controlling MCP use, see Control MCP use with IAM.

After March 17, 2026, when you enable the Cloud SQL Admin API (sqladmin.googleapis.com)`, the Cloud SQL remote MCP server is enabled automatically.

The Cloud SQL remote MCP server is in Preview.

Control of MCP use with organization policies is deprecated. After March 17, 2026, organization policies that use the gcp.managed.allowedMCPServices constraint won't work, and you can control MCP use with IAM deny policies. For more information about controlling MCP use, see Control MCP use with IAM.

After March 17, 2026, when you enable the Cloud SQL Admin API (sqladmin.googleapis.com), the Cloud SQL remote MCP server is enabled automatically.

The Cloud SQL remote MCP server is in Preview.

Control of MCP use with organization policies is deprecated. After March 17, 2026, organization policies that use the gcp.managed.allowedMCPServices constraint won't work, and you can control MCP use with IAM deny policies. For more information about controlling MCP use, see Control MCP use with IAM.

New best practices are available for securing generative AI agents using Model Context Protocol (MCP) with Google Cloud databases. This guide covers key security measures like least privilege, native database controls, and secure agent design to help you build safer AI applications. For more information, see Best practices for securing agent interactions with Model Context Protocol.

New best practices are available for securing generative AI agents using Model Context Protocol (MCP) with Google Cloud databases. This guide covers key security measures like least privilege, native database controls, and secure agent design to help you build safer AI applications. For more information, see Best practices for securing agent interactions with Model Context Protocol.

New best practices are available for securing generative AI agents using Model Context Protocol (MCP) with Google Cloud databases. This guide covers key security measures like least privilege, native database controls, and secure agent design to help you build safer AI applications. For more information, see Best practices for securing agent interactions with Model Context Protocol.

Model endpoint management for Cloud SQL for MySQL and the integration of Cloud SQL for MySQL with Vertex AI are now generally available (GA).

By integrating your Cloud SQL for MySQL instance with Vertex AI, you can invoke online predictions and generate vector embeddings from models hosted in Vertex AI directly from your Cloud SQL instance.

With model endpoint management, you can build generative AI applications by integrating your databases with models from third-party providers like OpenAI using your own API keys. Model endpoint management lets you register and manage model endpoints for your MySQL instance, making your interactions with a wider range of ML models seamless.

You can now use the Cloud SQL remote MCP server. The Cloud SQL remote MCP server lets you interact easily with Cloud SQL instances from LLMs, AI applications, and AI-enabled development platforms.

This feature is in Preview.

You can now use the Cloud SQL remote MCP server. The Cloud SQL remote MCP server lets you interact easily with Cloud SQL instances from LLMs, AI applications, and AI-enabled development platforms.

This feature is in Preview.

You can now use the Cloud SQL remote MCP server. The Cloud SQL remote MCP server lets you interact easily with Cloud SQL instances from LLMs, AI applications, and AI-enabled development platforms.

This feature is in Preview.

You can now update the server certificate authority (CA) mode of an existing Cloud SQL instance. You can update existing instances that use the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA) to use the shared CA option (GOOGLE_MANAGED_CAS_CA) or the customer-managed CA option (CUSTOMER_MANAGED_CAS_CA).

For more information about the different server CA mode options, see Certificate authority (CA) hierarchies.

You can now update the server certificate authority (CA) mode of an existing Cloud SQL instance. You can update existing instances that use the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA) to use the shared CA option (GOOGLE_MANAGED_CAS_CA) or the customer-managed CA option (CUSTOMER_MANAGED_CAS_CA).

For more information about the different server CA mode options, see Certificate authority (CA) hierarchies.

You can now update the server certificate authority (CA) mode of an existing Cloud SQL instance. You can update existing instances that use the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA) to use the shared CA option (GOOGLE_MANAGED_CAS_CA) or the customer-managed CA option (CUSTOMER_MANAGED_CAS_CA).

For more information about the different server CA mode options, see Certificate authority (CA) hierarchies.

You can now assign database roles to built-in database users and IAM database users when you create or update users. For more information about assigning roles, see built-in database authentication or IAM database authentication.

You can now assign database roles to built-in database users and IAM database users when you create or update users. For more information about assigning roles, see built-in database authentication or IAM database authentication.

Cloud SQL for MySQL now supports performance capture to help you diagnose transient performance issues with your MySQL database. Performance capture lets you specify configurable thresholds for additional monitoring. If a threshold is reached, then performance capture takes snapshots of the database state, including in-flight transactions, InnoDB status, and, in the case of replication lag, detailed replication status. Performance capture outputs the snapshots in a log format so you can review the state of the instance when the problem occurred.

For more information, see Cloud SQL performance capture overview. Performance capture is in Preview.

Cloud SQL for MySQL 8.0.43 is now the default minor version of Cloud SQL for MySQL 8.0.

If you have automatic minor version upgrade enabled for your instance, then your instance is upgraded to the default minor version automatically during its regularly scheduled maintenance update.

For more information about automatic minor version upgrade, see Upgrade the database minor version of MySQL 8.0.

Cloud SQL for MySQL now supports fast clone operations within the same zone (GA).

For more information, see Clone an instance.

Cloud SQL for PostgreSQL now supports fast clone operations within the same zone (GA).

For more information, see Clone an instance.

You can build data agents that interact with the data in your database using conversational language. Use these data agents as tools to empower your applications. For more information, see Data agents overview. This feature is available in Preview, and access to it requires a sign-up.

You can build data agents that interact with the data in your database using conversational language. Use these data agents as tools to empower your applications. For more information, see Data agents overview. This feature is available in Preview, and access to it requires a sign-up.

Cloud SQL enhanced backups are now generally available (GA).

With enhanced backups, backups are managed and stored in a centralized backup management project that leverages the Backup and DR service, and provides enforced retention, granular scheduling, and longer retention.

Enhanced backups now also support point-in-time-recovery (PITR) after instance deletion.

For more information about the available options and their limitations, see Backup options. For more information about enhanced backups pricing, see Backup and DR pricing.

Cloud SQL enhanced backups are now generally available (GA).

With enhanced backups, backups are managed and stored in a centralized backup management project that leverages the Backup and DR service, and provides enforced retention, granular scheduling, and longer retention.

Enhanced backups now also support point-in-time-recovery (PITR) after instance deletion.

For more information about the available options and their limitations, see Backup options. For more information about enhanced backups pricing, see Backup and DR pricing.

Cloud SQL enhanced backups are now generally available (GA).

With enhanced backups, backups are managed and stored in a centralized backup management project that leverages the Backup and DR service, and provides enforced retention, granular scheduling, and longer retention.

Enhanced backups now also support point-in-time-recovery (PITR) after instance deletion.

For more information about the available options and their limitations, see Backup options. For more information about enhanced backups pricing, see Backup and DR pricing.

Cloud SQL for SQL Server integration with Microsoft Entra ID (Preview) provides centralized identity and access management (IAM) for your databases using your existing Microsoft Entra ID tenant.

To help prevent out-of-memory (OOM) events, you can enable managed buffer pool for Cloud SQL for MySQL 8.0 and later instances. When you enable managed buffer pool, Cloud SQL reduces the value of the innodb_buffer_pool_size configuration and frees up memory when memory usage is high, and the instance is in danger of an OOM event. After memory usage stabilizes at a lower value, MySQL increases the value of innodb_buffer_pool_size incrementally to its original value.

To enable managed buffer pool, your Cloud SQL instance must use a maintenance version of [$MYSQL_VERSION].R20251004.01_07 or later. You can't enable managed buffer pool for instances that use a shared core or for instances that are running MySQL 5.6 or MySQL 5.7.

For more information, see Enable managed buffer pool. Support for managed buffer pool is in Preview.

PostgreSQL version 18 is now generally available for Cloud SQL for PostgreSQL.

You can now use Database Migration Service with Cloud SQL for PostgreSQL when using PostgreSQL version 18.

To upgrade your instance to PostgreSQL 18, see Upgrade the database major version in-place.

The following extensions are also now available for PostgreSQL 18:

• pg_hint_plan