To get the latest product updates delivered to you, add the URL of this page to your
reader, or add the feed URL directly:
March 24, 2021
Support for europe-central2 (Warsaw ).
March 12, 2021
Cloud SQL for MySQL now supports the innodb_buffer_pool_size flag. To learn more about how to set this flag, see buffer pool size.
March 05, 2021
The following MySQL minor versions have been upgraded:
- MySQL 5.6.47 is upgraded to 5.6.50
- MySQL 5.7.25 is upgraded to 5.7.32
Cloud SQL for MySQL now supports flexible instance configurations. Compared to our predefined machine types, flexible instance configurations offer you the extra freedom to configure your instance with the specific number of vCPUs and GB of RAM that fits your workload. To set up a new instance with a flexible instance configuration, see our documentation here.
February 24, 2021
Cloud SQL now offers faster maintenance, with average connectivity loss lasting 90 seconds or less on average. See more about maintenance timelines.
February 10, 2021
The Cloud SQL Admin API v1beta4 is now generally available. The URL for the Admin API will continue to refer to v1beta4 for backward compatibility. To start using the Cloud SQL Admin API now, see Using the Cloud SQL Admin API.
January 13, 2021
Cloud SQL now exposes the metric
database/memory/total_usage. This metric provides visibility into the database working set (including buffer cache). You can find this metric in the Metrics explorer within the Monitoring dashboard.
For more information about
database/memory/total_usage, see Cloud SQL Metrics.
December 17, 2020
In Cloud SQL for MySQL, parallel replication is generally available for improving replication performance.
November 19, 2020
Cloud SQL for MySQL now supports retention settings for automated backups. You can configure retention of your automated backups for shorter or longer periods (1 to 365 days). The default setting remains 7 days.
Cloud SQL for MySQL now supports retention settings for point-in-time recovery. You have the option of retaining logs, used for point-in-time recovery, for shorter periods (1 to 7 days). The default setting is 7 days.
October 30, 2020
In Cloud SQL for MySQL, 80 supported flags that previously were in beta are now generally available.
October 21, 2020
Cloud SQL for MySQL supports binary logging on read replicas for MySQL versions 5.7 and 8.0.
October 12, 2020
Cloud SQL now offers "deny maintenance periods". With deny maintenance periods, you can prevent automatic maintenance from occurring during a specific time period. For example, the end-of-year holiday season is a time of peak load that requires heightened focus on infrastructure stability for many retail businesses. By setting a deny maintenance period from mid-October to mid-January, these businesses can prevent planned upgrades from Cloud SQL during their busiest time of year.
September 24, 2020
MySQL 5.6.42 is upgraded to 5.6.47.
September 21, 2020
Cloud SQL has upgraded Replicating from an external server to version 1.1. You can now:
- Replicate from sources where GTID is not enabled.
- Allow Cloud SQL to copy data directly from an external server to a Cloud SQL replica.
- Use new APIs that give you greater control to verify replication requirements, retry after making external server configuration changes, and remove the 30-minute limit for successful connectivity to an external server.
September 15, 2020
Cloud SQL now offers serverless export. With serverless export, Cloud SQL performs the export from a temporary instance. Offloading the export operation allows databases on the primary instance to continue to serve queries and perform other operations at the usual performance rate.
August 25, 2020
For information about the implementation of MySQL 8.0 on Cloud SQL, see the following topics:
- MySQL 8.0 authentication
- Differences between Cloud SQL and standard MySQL functionality
- Unsupported Cloud SQL feature in MySQL 8.0 for Cloud SQL
To get started using MySQL 8.0 on Cloud SQL, see Creating instances.
June 23, 2020
Committed use discounts (CUDs) are now available to purchase for Cloud SQL. CUDs provide discounted prices in exchange for your commitment to use a minimum level of resources for a specified term. With committed use discounts for Cloud SQL, you can earn a deep discount off your cost of use in exchange for committing to continuously use database instances in a particular region for a 1- or 3-year term. See the documentation for more details.
June 08, 2020
Support for asia-southeast2 region (Jakarta).
May 18, 2020
MySQL 5.6 minor version is upgraded to 5.6.42. MySQL 5.7 minor version is upgraded to 5.7.25.
May 04, 2020
As previously announced, Cloud SQL First Generation was deprecated on January 29, 2019. All First Generation instances have been migrated to Second Generation. In the documentation and in the Google Cloud Console, "MySQL Second Generation instances" are now referred to simply as "MySQL instances." For general information about this deprecation, see the existing deprecation notice.
April 20, 2020
Support for us-west4 region (Las Vegas).
March 24, 2020
Cloud SQL now supports 96-core machine types for MySQL, Postgres, and SQL Server instances. For pricing-related information, see the Pricing page.
March 16, 2020
Cloud SQL now supports read replicas in a different region than that of the primary instance, providing additional protection against regional outages and improving read performance by making replicas available closer to your application. To get started, see Cross-region replicas.
Cloud SQL instances using private IP are now accessible across regions, at the regular cross-region network egress cost.
February 27, 2020
MySQL 5.6.42 is now generally available in Cloud SQL. To start using MySQL 5.6.42, see Creating Instances.
February 24, 2020
Support for us-west3 region (Salt Lake City).
February 06, 2020
First Generation instances no longer can be created. As previously announced, Cloud SQL First Generation was deprecated on January 29, 2019. To improve performance, availability, and storage capacity, Cloud SQL Second Generation has replaced First Generation. For more information, see the existing deprecation notice and, if necessary, the information about upgrading an instance.
January 24, 2020
Support for asia-northeast3 region (Seoul).
December 17, 2019
Cloud SQL now supports VPC Service Controls, which let you add a service perimeter around the Cloud SQL Admin API and host project for Cloud SQL instances to reduce the risk of data exfiltration. To learn more about using VPC Service Controls with Cloud SQL, see Configuring VPC Service Controls.
December 13, 2019
You can now use Cloud VPN with Cloud SQL. To get started, see Using a VPN with Cloud SQL.
Connection organization policies for Cloud SQL give you the ability to set policies that control access to and from Cloud SQL instances. To learn more about this feature, see Connection organization policies. To use this feature, see Setting organization policies for Cloud SQL.
December 10, 2019
Cloud SQL now offers notifications for upcoming maintenance. 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 Finding and setting maintenance windows.
November 25, 2019
Cloud SQL now supports Access Transparency. As part of Google's long-term commitment to security and transparency, you can use Access Transparency, which provides you with logs of actions that Google staff have taken when accessing your data. To learn more about Access Transparency, see the Overview of Access Transparency.
November 19, 2019
Cloud SQL now supports customer-managed encryption keys (CMEK). With CMEK, you can encrypt Cloud SQL instances using a key you manage. To learn more about CMEK, see the Overview of customer managed encryption keys (CMEK). To start using CMEK, see Using customer-managed encryption keys (CMEK).
October 18, 2019
Cloud SQL Second Generation MySQL instances have a new high availability (HA) configuration. The new HA configuration, based on Google's Regional Disks, eliminates replication lag and, combined with automatic failover, provides isolation from many types of infrastructure, hardware, and software failures. Regional disks also ensure that all previously committed database transactions are persisted and available after failover, right up to the time of the failure.
The new high availability configuration is the default. You can continue to use the API to create instances with the legacy high availability configuration (using failover replicas) until the upgrade of existing instances occurs in early 2020. To learn how high availability now works for Second Generation MySQL instances, see the Overview of the high availability configuration. To enable high availability on existing instances, or to create new instances with high availability, see Enabling and disabling high availability on an instance.
June 25, 2019
This release increases the maximum data storage for instances of MySQL (MySQL Second Generation) and PostgreSQL. The maximum data storage is increased from 10,230 GB to 30,720 GB. For Cloud SQL storage limits, see Limits. You can limit your automatic storage increases; see Automatic storage increase limit.
May 24, 2019
Cloud SQL now allows you to specify a location for backups, and to restrict data to a single region. To learn about custom backup locations, see Custom backup locations. To learn how to set a custom location for a backup, see Setting and viewing a custom location for backups.
April 18, 2019
Support for asia-northeast2 region (Osaka, Japan).
April 03, 2019
March 11, 2019
Support for europe-west6 region (Zürich, Switzerland).
January 29, 2019
Cloud SQL Second Generation is replacing First Generation. Support for First Generation instances for MySQL is ending March 25th, 2020.
December 06, 2018
GA support for Private IP connectivity.
October 01, 2018
Support for asia-east2 region (Hong Kong).
Upgrade to Second Generation generally available for eligible First Generation MySQL instances.
September 01, 2018
Beta support for private IP (private services access) connectivity.
Proxy version 1.12 released.
July 01, 2018
Support for us-west2 region (Los Angeles).
June 01, 2018
Support for connecting from Cloud Functions Beta.
Support for europe-north1 region (Finland).
Support for rotating SSL certificates.
May 01, 2018
Support for asia-southeast1 region (Singapore).
March 01, 2018
Support for europe-west4 region (Netherlands).
February 01, 2018
Maximum concurrent connections to App Engine updated from 12 to 60.
January 01, 2018
MySQL 5.6 minor version upgraded to 5.6.36.
Support for northamerica-northeast1 region (Montréal).
November 01, 2017
October 01, 2017
Support for asia-south1 region (Mumbai).
Proxy version 1.11 released.
September 01, 2017
Support for 64-core machine types for MySQL instances and 64 cores for PostgreSQL instances.
Support for southamerica-east1 region (São Paulo).
August 01, 2017
Support for europe-west3 region (Frankfurt).
June 01, 2017
Support for labels.
Proxy version 1.10 released.
Support for australia-southeast1 region (Sydney).
Support for europe-west2 region (London).
May 01, 2017
GA support for Second Generation and PostgreSQL instances in version 157.0.0 of the
gcloud command-line tool. The
beta version is no longer required for these instances.
Support for us-west1 region (Oregon).
Support for us-east4 region (Northern Virginia).
April 01, 2017
Proxy version 1.09 released.
March 01, 2017
Support for 32-core machine types for MySQL instances.
Support for making MySQL general and slow query log files available through the Stackdriver Log Viewer.
February 01, 2017
December 01, 2016
November 01, 2016
Support for Northeastern Asia Pacific region (
MySQL 5.7 minor version upgraded to 5.7.14.
August 01, 2016
Cloud SQL Second Generation General Availability.
- Up to 16 cores and 104 GB RAM.
- SSD or HDD storage option with optional automatic storage increase capability.
- Optional high availability configuration (recommended for all production instances).
- Configurable maintenance window and maintenance timing.
- MySQL compatibility: