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.
]]>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.
]]>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.
]]>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.
]]>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.
]]>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.
]]>You can integrate Cloud SQL for SQL Server with customer-managed Active Directory (CMAD).
CMAD provides capabilities such as authentication and authorization. Joining an instance to a CMAD domain lets you sign in using Windows Authentication with an AD-based identity.
Customer-managed Active Directory (CMAD) is generally available (GA).
]]>Cloud SQL Enterprise edition now supports a new machine series called the N4 machine series. This machine series provides balanced price-to-performance and uses the Hyperdisk Balanced storage. You can create custom machine types for the N4 machine series with up to 80 vCPUs and up to 640 GB memory. The N4 machine series is generally available (GA).
For more information about the N4 machine series and its availability, see Machine series overview.
]]>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 now use Gemini's capabilities to fix errors in a query within Cloud SQL Studio (Preview).
]]>You can now provision, manage and query your databases using the dedicated Gemini CLI extension for Cloud SQL for SQL Server. The extension provides full lifecycle control of your database—from provisioning instances, to exploring schemas and troubleshooting issues—from your command-line interface.
For more information, see Use Cloud SQL for SQL Server with MCP, Gemini CLI, and other agents.
You can now retain point-in-time recovery (PITR) logs for an instance after its deletion for a specified retention period. These logs can be used to restore the deleted instance to a specific point in time. For more information, see Restore a deleted instance using PITR.
]]>You can have Cloud SQL create a Private Service Connect endpoint automatically. You can use this endpoint to access Cloud SQL instances through a VPC network. For more information, see Create a Private Service Connect endpoint automatically.
This feature is now generally available (GA).
]]>You can now enable your instance to take a final backup at instance deletion and define its retention period by setting the final backup instance setting.
You can also create a custom organization policy to define final backup instance settings. For more information, see Final backup.
]]>Max degree of parallelism (MAXDOP) is a Microsoft database flag available for use in Cloud SQL for SQL Server. This flag lets you limit the maximum number of threads used when running a single query in a parallel plan.
You can save and manage SQL queries in Cloud SQL Studio. This feature is in Preview. For more information, see Saved queries overview.
]]>Now you can create an IPv6 endpoint for Private Service Connect (PSC) connections. For more information, see Connect to an instance using Private Service Connect.
Now you can use Private Service Connect backends, as an alternative to Private Service Connect endpoints, to access Cloud SQL instances.
You can no longer set a deny maintenance period for instances that are running a maintenance version older than 12 months. To update your instance, perform self-service maintenance or wait until the next maintenance window to update your instance automatically. For more information about maintenance, see Maintenance updates on Cloud SQL instances.
]]>Cloud SQL now supports Private Service Connect (PSC) outbound connectivity. With PSC outbound connectivity, you can attach a PSC interface to your existing Cloud SQL PSC-enabled instances to allow your instances to make outbound connections to your network. For more information, see PSC outbound connections.
]]>Cloud SQL now offers planned maintenance and machine tier upgrades for your Cloud SQL Enterprise plus instances with near-zero downtime for eligible instances.
For more information, see Maintenance updates on Cloud SQL instances.
]]>Cloud SQL now offers two options of backup services to manage your instance's backups:
Enhanced backups (Preview): 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.
Standard backups (existing option): backups are created, managed, and stored in the same project as your Cloud SQL instances.
You can choose between these options based on your instance's requirements and needs. Although instances can't use both backup options at the same time, Cloud SQL gives you the ability to switch between these backup options as necessary.
For more information about the available options and their limitations, see Backup options.
]]>Cloud SQL for SQL Server now offers Active Directory support for write endpoints. For more information, see Write endpoints across forests.
]]>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.
]]>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.