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.
]]>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.
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 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.
]]>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.
]]>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.
]]>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.
]]>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 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 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.
]]>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.
]]>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.6 is upgraded to MySQL 8.4.7. For more information, see the MySQL 8.4.7 Release Notes.
]]>Cloud SQL for MySQL now lets you have more control over the number of results
that are returned when you perform an ANN vector search with filters.
You can use iterative filtering when the selective filters of the
WHERE clause in your ANN search query produce fewer results
than the number of results specified in your LIMIT clause.
To enable iterative filtering for your ANN search query, set the
cloudsql_vector_iterative_filtering flag to ON.
You can set the flag at a session or global level.
To enable and use iterative filtering for your ANN search query, you must have
[MYSQL_$VERSION].R20251004.01_07
or later installed on your MySQL instance.
For more information, see Search approximate nearest neighbors (ANN).
]]>Cloud SQL for MySQL now supports minor version 8.0.44. To upgrade your existing instance to the new version, see Upgrade the database minor version.
]]>The rollout of the following minor versions, extension versions, and plugin versions is complete:
Minor versions
Extensions and plugins
To use these versions of the extensions, update your instance to [PostgreSQL version].R20250112.01_14.
If you use a maintenance window, then the updates to the minor, extension, and plugin versions happen according to the timeframe that you set in the window. Otherwise, the updates occur within the next few weeks.
For more information on checking your maintenance version, see Self-service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.
]]>You can now include replicas when you perform an in-place major version upgrade using gcloud or the Cloud SQL Admin API. For more information, see Upgrade the database major version in-place.
]]>Cloud SQL for MySQL vector search is now generally available. After you store vector embeddings in a table, you can perform K-nearest neighbor (KNN) searches against your vector dataset. You can also add a vector search index to perform approximate nearest neighbor (ANN) searches.
For more information, see Vector search.
]]>You can now migrate data from Microsoft Azure to Cloud SQL. For more information, see Configure Cloud SQL and the external server for replication.
You can now migrate data from Microsoft Azure to Cloud SQL. For more information, see Configure Cloud SQL and the external server for replication.
]]>As of January 13, 2025, the legacy configuration for high availability (HA) is deprecated for all Cloud SQL for MySQL instances. You can no longer create instances with the legacy HA configuration, and you can no longer enable the legacy HA configuration on existing instances. In addition, after January 13, 2025, legacy HA instances are no longer covered by the Cloud SQL SLA.
We recommend that you update your remaining legacy HA instances as soon as possible to the current HA configuration. You can do so by following the instructions in Update an instance from legacy to current high availability.
Starting on May 1, 2025, Cloud SQL will begin updating any instances that use the legacy high availability configuration to use the current regional persistent disk-based high availability configuration automatically.
]]>The rollout of the following minor versions, extension versions, and plugin versions is complete:
Minor versions
ALTER {ROLE|DATABASE} SET role command that's present in PostgreSQL version 12.22. For more information, see the PostgreSQL 12.22 release notes.Extension and plugin versions
To use these versions of the extensions, update your instance to one of the following:
POSTGRES_17_0.R20241011.00_11 (for PostgreSQL instances, version 17)[PostgreSQL version].R20240910.01_31 (for PostgreSQL instances, versions 12 to 16)If you use a maintenance window, then the updates to the minor, extension, and plugin versions happen according to the timeframe that you set in the window. Otherwise, the updates occur within the next few weeks.
For more information on checking your maintenance version, see Self-service maintenance. To find your maintenance window or to manage maintenance updates, see Find and set maintenance windows.
]]>You can now enable query insights for Cloud SQL Enterprise Plus edition. When you enable query insights for Enterprise Plus, you can access additional features in query insights such as 30 days of metrics retention, granular query plan details, and a higher query length limit.
For more information, see Use query insights to improve query performance. Query insights for Cloud SQL Cloud SQL Enterprise Plus edition is in Preview.
You can now enable query insights for Cloud SQL Enterprise Plus edition. When you enable query insights for Enterprise Plus, you can access additional features in query insights such as 30 days of metrics retention, granular query plan details, and a higher query length limit.
For more information, see Use query insights to improve query performance. Query insights for Cloud SQL Cloud SQL Enterprise Plus edition is in Preview.
You can use the following observability dashboards in Cloud SQL for SQL Server to monitor, analyze, and diagnose issues with your instances, databases, and queries:
Both of these dashboards are available to you in the Google Cloud Console. The System insights dashboard displays the metrics for the resources that your instance is using and can help you analyze the performance of your instance. For more information, see Use system insights to improve system performance. System insights is generally available (GA).
The Query insights dashboard helps you detect problems with queries in your Cloud SQL databases. The dashboard also provides you with the ability to monitor active queries and view index advisor recommendations. For more information, see Use query insights to improve query performance. Query insights for Cloud SQL for SQL Server is in Preview.
You can enable query insights for Cloud SQL Enterprise Plus edition. When you enable query insights for Enterprise Plus, you can access additional features in query insights such as 30 days of metrics retention, granular query plan details, and a higher query length limit. The query insights for Cloud SQL Enterprise Plus edition, index advisor, and active queries features are also in Preview.
]]>Cloud SQL now offers notifications for maintenance that's either started or completed. See the Overview of maintenance on Cloud SQL instances. To find out how to sign up for notifications and check your instances for upcoming maintenance, see Find and set maintenance windows.
Cloud SQL now offers notifications for maintenance that's either started or completed. See the Overview of maintenance on Cloud SQL instances. To find out how to sign up for notifications and check your instances for upcoming maintenance, see Find and set maintenance windows.
Cloud SQL now offers notifications for maintenance that's either started or completed. See the Overview of maintenance on Cloud SQL instances. To find out how to sign up for notifications and check your instances for upcoming maintenance, see Find and set maintenance windows.
]]>Cloud SQL Enterprise Plus edition now supports the following regions:
africa-south1 (Johannesburg)asia-east2 (Hong Kong)europe-west10 (Berlin)Cloud SQL Enterprise Plus edition now supports the following regions:
africa-south1 (Johannesburg)asia-east2 (Hong Kong)europe-west10 (Berlin)Cloud SQL Enterprise Plus edition now supports the following regions:
africa-south1 (Johannesburg)asia-east2 (Hong Kong)europe-west10 (Berlin)Cloud SQL for MySQL now supports minor version 8.0.40. To upgrade your existing instance to the new version, see Upgrade the database minor version.
]]>You can now use the Network Connectivity Center hub to propagate Private Service Connect endpoints of Cloud SQL instances in a VPC network. All endpoints in this network become accessible transitively to other spoke VPC networks through the hub. This feature is available in Preview.
You can now use the Network Connectivity Center hub to propagate Private Service Connect endpoints of Cloud SQL instances in a VPC network. All endpoints in this network become accessible transitively to other spoke VPC networks through the hub. This feature is available in Preview.
You can now use the Network Connectivity Center hub to propagate Private Service Connect endpoints of Cloud SQL instances in a VPC network. All endpoints in this network become accessible transitively to other spoke VPC networks through the hub. This feature is available in Preview.
]]>You can now create instances with both private services access and Private Service Connect enabled for them. You can also enable Private Service Connect for existing private services access instances. This feature is available in Preview. For more information, see Configure both private services access and Private Service Connect.
You can now create instances with both private services access and Private Service Connect enabled for them. You can also enable Private Service Connect for existing private services access instances. This feature is available in Preview. For more information, see Configure both private services access and Private Service Connect.
You can now create instances with both private services access and Private Service Connect enabled for them. You can also enable Private Service Connect for existing private services access instances. This feature is available in Preview. For more information, see Configure both private services access and Private Service Connect.
]]>You can now set up AlloyDB clusters using a copy of your Cloud SQL for PostgreSQL backup. This feature is in Preview. For more information, see Migrate from Cloud SQL for PostgreSQL to AlloyDB.
]]>You can now authenticate to Cloud SQL Studio by using IAM database authentication.
For more information about authentication in Cloud SQL Studio, see Manage your data using Cloud SQL Studio.
You can now authenticate to Cloud SQL Studio by using IAM database authentication.
For more information about authentication in Cloud SQL Studio, see Manage your data using Cloud SQL Studio.
]]>For Cloud SQL Enterprise Plus edition instances, advanced disaster recovery (DR) is now generally available (GA). For more information, see Advanced disaster recovery (DR) and Use advanced disaster recovery (DR).
The write endpoint feature is now available in Preview. This endpoint is a global domain name service (DNS) name. This name resolves to the IP address of the current primary Cloud SQL instance that's enabled with private services access.
By using a write endpoint, you can avoid having to make application connection changes after performing a switchover or replica failover operation to test or mitigate a regional failure. For more information, see Configure private IP.
The write endpoint feature is now available in Preview. This endpoint is a global domain name service (DNS) name. This name resolves to the IP address of the current primary Cloud SQL instance that's enabled with private services access.
By using a write endpoint, you can avoid having to make application connection changes after performing a switchover or replica failover operation to test or mitigate a regional failure. For more information, see Configure private IP.
For Cloud SQL Enterprise Plus edition instances, you can now use advanced disaster recovery (DR) to simplify recovery and fallback processes after you perform a cross-regional failover. With advanced DR, you can:
You can also use switchover to simulate disaster recovery without data loss. You can use advanced DR on Cloud SQL for PostgreSQL version 12, 13, 14, 15, or 16.
For more information, see Advanced disaster recovery (DR) and Use advanced disaster recovery (DR). This feature is generally available (GA).
]]>