Cloud SQL for MySQL
- Fully managed MySQL Community Edition databases in the cloud.
- Cloud SQL instances support MySQL 8.0, 5.7 (default), and 5.6, and provide up to 624 GB of RAM and 64 TB of data storage, with the option to automatically increase the storage size, as needed.
- Create and manage instances in the Google Cloud Console.
- Instances available in the Americas, EU, Asia, and Australia. See all locations.
- Customer data encrypted on Google's internal networks and in database tables, temporary files, and backups.
- Support for secure external connections with the Cloud SQL Auth proxy or with the SSL/TLS protocol.
- Support for private IP (private services access).
- Data replication between multiple zones with automatic failover.
- Import and export databases using
mysqldump, or import and export CSV files.
- Support for MySQL wire protocol and standard MySQL connectors.
- Automated and on-demand backups and point-in-time recovery.
- Instance cloning.
- Integration with Google Cloud's operations suite logging and monitoring.
- ISO/IEC 27001 compliant.
You can use Cloud SQL for MySQL with App Engine applications running in the flexible environment that are written in C#, Go, Java, Node.js, PHP, Python, and Ruby. You can also use Cloud SQL for MySQL with external applications using the standard MySQL protocol.
How you can connect to Cloud SQL for MySQL instances
You can connect to a Cloud SQL instance for MySQL from:
mysqlclient. Learn more.
- Third-party tools like SQL Workbench or Toad for MySQL. Learn more.
- External applications. Learn more.
- App Engine applications. Learn more.
- Applications running on Compute Engine. Learn more.
- Applications running on Google Kubernetes Engine. Learn more.
- Cloud Functions. Learn more.
- Cloud Run. Learn more.
- Google Apps Script scripts Learn more.
Connecting to Cloud SQL by using Private Google access is not supported. Private services access is supported. For more information, see Private Access Options for Services.
User management in MySQL for Cloud SQL 8.0
Due to changes in MySQL 8.0, you can't use
DELETE for MySQL
users management. You also can't modify user privileges using
DELETE statements. Instead, use
DROP USER and
REVOKE statements to modify user privileges. For more information,
see Account management notes.
Note: Disregard information under Account management notes about running
mysql_upgrade to upgrade to version 8.0. Instead, upgrade using the procedure
in Upgrading MySQL on an instance.
Differences between Cloud SQL and standard MySQL functionality
In general, the MySQL functionality provided by a Cloud SQL instance is the same as the functionality provided by a locally-hosted MySQL instance. However, there are a few differences between a standard MySQL instance and a Cloud SQL for MySQL instance.
Unsupported MySQL features
The following feature is unsupported for MySQL for Cloud SQL 5.6 and 5.7:
The following features are unsupported for MySQL for Cloud SQL 8.0:
- InnoDB memcached plugin
- X plugin
- Clone plugin
- InnoDB data-at-rest encryption
- validate_password component
The following SQL statements generate an error with the message"Error 1290: The MySQL server is running with the Google option so it cannot execute this statement":
LOAD DATA INFILE
LOAD DATA LOCAL
SELECT ... INTO OUTFILE
SELECT ... INTO DUMPFILE
INSTALL PLUGIN ...
CREATE FUNCTION ... SONAME ...
The following statements are not supported because MySQL instances use GTID replication:
CREATE TABLE ... SELECTstatements
- Transactions or statements that update both transactional and nontransactional tables
The following statement is unsupported in MySQL for MySQL for Cloud SQL 5.6 and 5.7, but is supported in MySQL for Cloud SQL 8.0.
CREATE TEMPORARY TABLEstatements inside transactions
For more information, see the MySQL documentation.
Unsupported client program features
If you want to import databases with binary data into your Cloud SQL for MySQL instance, you must use the
hex-blobis not a required flag when you are using a local MySQL server instance and the
mysqlclient, it is required if you want to import any databases with binary data into your Cloud SQL instance. For more information about importing data, see Importing Data.
Not all MySQL options and parameters are enabled for editing as Cloud SQL flags.
To request the addition of a configurable Cloud SQL flag, use the Cloud SQL Discussion group.
InnoDB is the only supported storage engine. For help with converting tables from MyISAM to InnoDB, see the MySQL documentation.
MySQL options preset on Cloud SQL
Cloud SQL runs MySQL with a specific set of options. If an option might impact how your applications work, we note it here for your information.
This flag impacts how hostnames are resolved for client connections. Learn more.
This flag reports whether binary logging is enabled. If the
--log-bin option is
used, then the value of this variable is
ON; otherwise it is
MySQL 8.0 authentication
MySQL 8.0 for Cloud SQL uses
mysql_native_password as the default
authentication plugin for new users instead of
mysql_native_password plugin is the default for MySQL 5.6 and 5.7 users.
If you want new users to use the
caching_sha2_password plugin as the default authentication, you can configure
your instance flag for
default_authentication_plugin to use
To configure existing users to use
caching_sha2_password, use the
command to change the authentication plugin.
Users that have the
caching_sha2_password authentication might need to use
flag when connecting. For details, see the MySQL docs section on
Using SHA-2 Pluggable Authentication.
Changes to MySQL system flags in Cloud SQL
On some MySQL system flags, Cloud SQL uses values that are different from the default value. You can't change these system flags. For a list of flags, see MySQL system flags changed in Cloud SQL.
Unsupported Cloud SQL feature in MySQL 8.0 for Cloud SQL
MySQL 8.0 for Cloud SQL does not support the legacy version of MySQL high availability (HA) configuration that uses failover replicas. It supports the new regional HA configuration.