Cloud SQL for SQL Server now offers the maximum server memory recommender.
Database instances running with an allocation of memory that's either too low or too high might experience performance issues.
The max server memory (mb) flag limits the amount of memory that Cloud SQL can allocate for its internal pools. You can manually set a value for this flag, or omit the flag and let Cloud SQL manage memory limits for you automatically.
For more information, see Optimize maximum server memory usage.
]]>Cloud SQL for SQL Server now extends query insights and index advisor support to read replicas.
]]>You can now create an instance with both private services access and Private Service Connect enabled. You can also enable Private Service Connect on an existing private services access instance. This feature is now generally available (GA).
For more information, see Configure both private services access and Private Service Connect.
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].R20250302.00_19.
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 create an instance with both private services access and Private Service Connect enabled. You can also enable Private Service Connect on an existing private services access instance. This feature is now generally available (GA).
For more information, see Configure both private services access and Private Service Connect.
You can now create an instance with both private services access and Private Service Connect enabled. You can also enable Private Service Connect on an existing private services access instance. This feature is now generally available (GA).
For more information, see Configure both private services access and Private Service Connect.
]]>Cloud SQL for MySQL now supports minor version 8.0.42. To upgrade your existing instance to the new version, see Upgrade the database minor version.
You can now use advanced disaster recovery (DR) for your Private Service Connect (PSC) enabled Cloud SQL Enterprise Plus edition instances. With advanced DR, you can:
You can also use switchover to simulate disaster recovery without data loss. For more information, see Use advanced disaster recovery (DR). This feature is generally available (GA).
You can now use advanced disaster recovery (DR) for your Private Service Connect (PSC) enabled Cloud SQL Enterprise Plus edition instances. With advanced DR, you can:
You can also use switchover to simulate disaster recovery without data loss. For more information, see Use advanced disaster recovery (DR). This feature is generally available (GA).
]]>Cloud SQL for SQL Server now supports TLS connections to Active Directory endpoints without requiring server certificate trust or the use of IP addresses. Existing server certificates will need to be rotated to use this feature.
]]>If you create an instance using the Google Cloud Console, then the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA) option is now the default server certificate authority (CA) mode for your Cloud SQL instance.
For users of the Cloud SQL Auth Proxy:
serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.13.0 or later.serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.14.3 or later.If you create an instance using the Google Cloud Console, then the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA) option is now the default server certificate authority (CA) mode for your Cloud SQL instance.
For users of the Cloud SQL Auth Proxy:
serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.13.0 or later.serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.14.3 or later.If you create an instance using the Google Cloud Console, then the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA) option is now the default server certificate authority (CA) mode for your Cloud SQL instance.
For users of the Cloud SQL Auth Proxy:
serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.13.0 or later.serverCaMode setting, then on the client side, you must use Cloud SQL Auth Proxy version 2.14.3 or later.You can migrate to AlloyDB for PostgreSQL using your Cloud SQL for PostgreSQL backup (GA). The Google Cloud CLI is also supported. For more information, see Migrate from Cloud SQL for PostgreSQL to AlloyDB.
]]>Cloud SQL for Enterprise Plus edition supports AI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues like slow queries and high load for your instances in a guided manner. To use AI-assisted troubleshooting, you need Gemini Cloud Assist and query insights for Enterprise Plus edition. AI-assisted troubleshooting is available in Preview.
]]>You can now set up custom DNS names by configuring the custom subject alternative name (SAN) for your instance. After you set up DNS name resolution, you can connect to your Cloud SQL instance using the custom DNS name instead of using an IP address. This feature is available only for instances that are configured with the customer-managed certificate authority (CA) (CUSTOMER_MANAGED_CAS_CA) option as its server CA mode.
Custom SAN configuration for instances is generally available (GA).
You can now set up custom DNS names by configuring the custom subject alternative name (SAN) for your instance. After you set up DNS name resolution, you can connect to your Cloud SQL instance using the custom DNS name instead of using an IP address. This feature is available only for instances that are configured with the customer-managed certificate authority (CA) (CUSTOMER_MANAGED_CAS_CA) option as its server CA mode.
Custom SAN configuration for instances is generally available (GA).
You can now set up custom DNS names by configuring the custom subject alternative name (SAN) for your instance. After you set up DNS name resolution, you can connect to your Cloud SQL instance using the custom DNS name instead of using an IP address. This feature is available only for instances that are configured with the customer-managed certificate authority (CA) (CUSTOMER_MANAGED_CAS_CA) option as its server CA mode.
Custom SAN configuration for instances is generally available (GA).
]]>Cloud SQL gives you the flexibility to choose between three CA hierarchy options when you create a Cloud SQL instance.
You can choose between the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA), the shared CA (GOOGLE_MANAGED_CAS_CA), or the customer-managed CA (CUSTOMER_MANAGED_CAS_CA) options as the server certificate authority (CA) mode for your instance. If you create an instance using the Google Cloud Console, then the shared CA option, (GOOGLE_MANAGED_CAS_CA), is the default configuration. If you create an instance using gcloud, the Cloud SQL Admin REST API, or Terraform, then the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA) is the default configuration.
The shared CA and customer-managed CA options are now generally available (GA).
Cloud SQL gives you the flexibility to choose between three CA hierarchy options when you create a Cloud SQL instance.
You can choose between the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA), the shared CA (GOOGLE_MANAGED_CAS_CA), or the customer-managed CA (CUSTOMER_MANAGED_CAS_CA) options as the server certificate authority (CA) mode for your instance. If you create an instance using the Google Cloud Console, then the shared CA option, (GOOGLE_MANAGED_CAS_CA), is the default configuration. If you create an instance using gcloud, the Cloud SQL Admin REST API, or Terraform, then the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA) is the default configuration.
The shared CA and customer-managed CA options are now generally available (GA).
Cloud SQL gives you the flexibility to choose between three CA hierarchy options when you create a Cloud SQL instance.
You can choose between the per-instance CA (GOOGLE_MANAGED_INTERNAL_CA), the shared CA (GOOGLE_MANAGED_CAS_CA), or the customer-managed CA (CUSTOMER_MANAGED_CAS_CA) options as the server certificate authority (CA) mode for your instance. If you create an instance using the Google Cloud Console, then the shared CA option, (GOOGLE_MANAGED_CAS_CA), is the default configuration. If you create an instance using gcloud, the Cloud SQL Admin REST API, or Terraform, then the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA) is the default configuration.
The shared CA and customer-managed CA options are now generally available (GA).
]]>The rollout of the following extension versions and plugin versions is complete:
Extensions and plugins
pg_partman is upgraded from 5.0.1 to 5.2.4 (for PostgreSQL versions 14 and later).To use this version of the extension, update your instance to [PostgreSQL version].R20250302.00_10.
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.
]]>Private Service Connect endpoint propagation is now generally available (GA). You can use the Network Connectivity Center hub to propagate the Private Service Connect endpoints of your Cloud SQL instances in a VPC network.
Private Service Connect endpoint propagation is now generally available (GA). You can use the Network Connectivity Center hub to propagate the Private Service Connect endpoints of your Cloud SQL instances in a VPC network.
Private Service Connect endpoint propagation is now generally available (GA). You can use the Network Connectivity Center hub to propagate the Private Service Connect endpoints of your Cloud SQL instances in a VPC network.
]]>Cloud SQL for MySQL 8.0.40 is now the default minor version. To upgrade your existing instance to the new version, see Upgrade the database minor version.
]]>Cloud SQL Enterprise Plus edition now supports a new machine series called the C4A machine series, which provides optimized price-performance and delivers predictable high performance for high demand Cloud SQL workloads. C4A uses a new type of storage called Hyperdisk Balanced, and offers up to 72 vCPUs and up to 576 GB memory. The C4A machine series is available in Preview.
For more information about the C4A machine series and its availability, see Machine series overview.
Query insights for Cloud SQL Enterprise Plus edition is now generally available (GA) for your Cloud SQL Enterprise Plus edition for MySQL instances. Query insights for Cloud SQL Enterprise Plus edition offers fine-grained metrics such as wait events and granular query plan samples for faster root-cause analysis and intelligent index recommendations.
For more information, see Use query insights to improve query performance.
Cloud SQL for Enterprise Plus edition supports AI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues like slow queries and high load for your instances in a guided manner. To use AI-assisted troubleshooting, you need Gemini Cloud Assist and query insights for Enterprise Plus edition. AI-assisted troubleshooting is available in Preview.
Cloud SQL Enterprise Plus edition now supports a new machine series called the C4A machine series, which provides optimized price-performance and delivers predictable high performance for high demand Cloud SQL workloads. C4A uses a new type of storage called Hyperdisk Balanced, and offers up to 72 vCPUs and up to 576 GB memory. The C4A machine series is available in Preview.
For more information about the C4A machine series and its availability, see Machine series overview.
Query insights for Cloud SQL Enterprise Plus edition is now generally available (GA) for your Cloud SQL Enterprise Plus edition for PostgreSQL instances. Query insights for Cloud SQL Enterprise Plus edition offers fine-grained metrics such as wait events and granular query plan samples for faster root-cause analysis and intelligent index recommendations.
For more information, see Use query insights to improve query performance.
Cloud SQL for Enterprise Plus edition supports AI-assisted troubleshooting. With AI-assisted troubleshooting, you can resolve complex database performance issues like slow queries and high load for your instances in a guided manner. To use AI-assisted troubleshooting, you need Gemini Cloud Assist and query insights for Enterprise Plus edition. AI-assisted troubleshooting is available in Preview.
Query insights for Cloud SQL Enterprise edition and Cloud SQL Enterprise Plus edition is now generally available (GA) for Cloud SQL for SQL Server. You can also now view the query details, query plans, and statistical query execution charts for your top queries.
For more information, see Use query insights to improve query performance.
]]>Cloud SQL now supports the Enterprise Plus recommender. Based on your application workloads and resource utilization, the recommender helps you optimize performance by identifying SQL Server instances that might see performance improvements when upgraded to Cloud SQL Enterprise Plus edition.
]]>The rollout of the following extension versions and plugin versions is complete:
Extensions and plugins
To use these versions of the extensions, update your instance to [PostgreSQL version]. R20250302.00_04.
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 integrate Cloud SQL for MySQL and Vertex AI (in Preview). This allows you to invoke predictions and generate vector embeddings using models hosted in Vertex AI. To use this integration, update your instance to [MySQL version].R20250304.00_01.
For more information, see Integrate Cloud SQL with Vertex AI.
]]>Cloud SQL now supports Managed Connection Pooling (MCP) in Preview, which lets you scale your workloads by optimizing resource utilization for your Cloud SQL instances using pooling. To use Managed Connection Pooling, update your instance to [MySQL version].R20250302.00_04.
For more information, see Managed Connection Pooling overview.
Cloud SQL now supports Managed Connection Pooling (MCP) in Preview, which lets you scale your workloads by optimizing resource utilization for your Cloud SQL instances using pooling. To use Managed Connection Pooling, update your instance to [PostgreSQL version].R20250302.00_04.
For more information, see Managed Connection Pooling overview.
]]>When you create a Cloud SQL for SQL Server instance, version SQL Server 2022 Standard is now the default.
]]>Cloud SQL read pools provide operational simplicity and scaling for your large read workloads.
Read pools provide a single endpoint in front of up to 20 read pool nodes and automatically load balance traffic.
You can scale your read pool in several ways:
For more information, see About read pools.
Cloud SQL read pools provide operational simplicity and scaling for your large read workloads.
Read pools provide a single endpoint in front of up to 20 read pool nodes and automatically load balance traffic.
You can scale your read pool in several ways:
For more information, see About read pools.
]]>Cloud SQL now lets you retain existing backups after an instance is deleted. These consist of on-demand and automatic backups created when the instance was live. For more information, see Retained backups.
Cloud SQL now lets you retain existing backups after an instance is deleted. These consist of on-demand and automatic backups created when the instance was live. For more information, see Retained backups.
Cloud SQL now lets you retain existing backups after an instance is deleted. These consist of on-demand and automatic backups created when the instance was live. For more information, see Retained backups.
]]>You can now use PITR to restore a Cloud SQL for MySQL instance that isn't available.
]]>Cloud SQL for SQL Server supports transparent data encryption (TDE) to encrypt data stored in your Cloud SQL for SQL Server instances.
TDE automatically encrypts data before it is written to storage, and automatically decrypts data when the data is read from storage.
TDE provides another layer of encryption in addition to Google's default offering of encryption for data at rest and Google's optional offering of customer-managed encryption keys (CMEK). TDE helps you meet regulatory compliance requirements and supports import or export operations of TDE encrypted backups. For more information, see About transparent data encryption.
]]>You can use PITR to restore a Cloud SQL for SQL Server instance that isn't available.
]]>Cloud SQL for MySQL introduces a set of improvements that adjust MySQL configurations dynamically based on workload demands and underlying infrastructure to optimize write performance and reduce latency. By default these improvements are enabled for all new Cloud SQL Enterprise Plus edition instances that you create or that you upgrade to from Cloud SQL Enterprise edition. Existing Cloud SQL Enterprise Plus instances that are updated with maintenance version [MySQL_version].R20250304.00_01 will also enable these improvements automatically.
For more information about these improvements, see Configure database flags.
]]>Cloud SQL Enterprise edition now supports the europe-north2 (Stockholm) region.
Cloud SQL for MySQL now supports minor version 8.0.41. To upgrade your existing instance to the new version, see Upgrade the database minor version.
Cloud SQL Enterprise edition now supports the europe-north2 (Stockholm) region.
Cloud SQL Enterprise edition now supports the europe-north2 (Stockholm) region.
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.
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.
]]>You can now export or import all user databases in an instance using a directory-formatted, parallel export or import operation.
]]>You can now create a final backup of your data before you delete a Cloud SQL instance. You can use the final backup to restore your data to a new instance. This way, you can recover your data after you delete the instance. For more information, see About Cloud SQL backups.
You can now create a final backup of your data before you delete a Cloud SQL instance. You can use the final backup to restore your data to a new instance. This way, you can recover your data after you delete the instance. For more information, see About Cloud SQL backups.
You can now create a final backup of your data before you delete a Cloud SQL instance. You can use the final backup to restore your data to a new instance. This way, you can recover your data after you delete the instance. For more information, see About Cloud SQL backups.
]]>