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
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 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 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.
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.
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.
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:
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.
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.
]]>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):
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:
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.
]]>