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.
]]>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_planpgroutinganonymizerpg_wait_samplingtds_fdwplpgsql_checkFor more information about these extensions, see Configure PostgreSQL extensions.
]]>Cloud SQL for PostgreSQL now supports Vector assist (Preview).
Vector assist is a Cloud SQL for PostgreSQL extension that simplifies the deployment and management of your Cloud SQL vector workloads. It helps you set up production-ready vector search capabilities, such as embedding generation, query optimization, and index creation.
For more information about vector assist, how it works, and its limitations, see Vector assist overview.
The rollout of the following minor version and extension upgrades is complete:
Minor versions
Extensions
Pgvector is upgraded from 0.8.0 to 0.8.1.To use these versions of the extensions and plugins, update your instance to
[PostgreSQL version].R20251004.01_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.
]]>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 now offers a free trial instance for both existing and new Google Cloud customers. A free trial instance lets you test advanced Cloud SQL capabilities and features for up to 30 days without any financial commitment.
For information about a free trial instance, and its inclusions and conditions, see Free trial instance overview.
Cloud SQL now offers a free trial instance for both existing and new Google Cloud customers. A free trial instance lets you test advanced Cloud SQL capabilities and features for up to 30 days without any financial commitment.
For information about a free trial instance, and its inclusions and conditions, see Free trial instance overview.
]]>