Google Cloud SQL is an easy-to-use service that delivers fully managed MySQL databases. It lets you hand off to Google the mundane, but necessary and often time consuming tasks — like applying patches and updates, managing backups and configuring replications — so you can put your focus on building great applications. And because we use standard MySQL, it’s easy to connect from just about any application, anywhere. It has all the capabilities and functionality of MySQL, with a few additional features and a few unsupported features as listed below. Google Cloud SQL is easy to use-- it doesn't require any software installation or maintenance.
You can connect to a Google Cloud SQL instance from:
- MySQL Client
- Third-party tools like SQL Workbench or Toad for MySQL
- External applications using standard MySQL database drivers
- Google App Engine applications
- Google Apps Script scripts
Features and Restrictions
You can use Google Cloud SQL for Google App Engine applications that are written in Java, Python, PHP, and Go, and with external applications using the standard MySQL protocol. You can also access Google Cloud SQL using MySQL Client and other administration and reporting tools that work with MySQL databases.
- Fully managed MySQL 5.5 and 5.6 databases in the cloud
- First Generation instances can have up to 16GB of RAM and 500GB data storage.
- Second Generation instances can have up to 104GB of RAM and 10TB data storage.
- Create and manage instances in the Google Cloud Platform Console
- Instances available in US, EU, or Asia
- Customer data is encrypted when on Google’s internal networks and when stored in database tables, temporary files, and backups
- 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
- Support for connecting with the Secure Sockets Layer (SSL) protocol
- Automated backups and point-in-time recovery
- ISO/IEC 27001 compliant
- User defined functions are not supported
- The following MySQL statements are not supported:
LOAD DATA INFILE
LOAD DATA LOCAL INFILEis supported.
SELECT ... INTO OUTFILE/DUMPFILE
INSTALL/UNINSTALL PLUGIN ...
CREATE FUNCTION ...
SUPERprivilege is not supported.
- The following MySQL Client Program features are not supported:
mysqlimportwithout using the
--localoption. This is due to the
LOAD DATA INFILErestriction. If you need to load data remotely, use the Cloud SQL import function.
--taboption or options that are used with
--tab. This is because the FILE privilege is not granted for instance users. All other mysqlimport options are supported.
Announcing Cloud SQL Second Generation (beta)
Cloud SQL Second Generation instance types are the latest version for Google Cloud SQL. These instances support most of the features of First Generation instances, and offer higher performance and storage capacity at a lower cost. Advantages of using Cloud SQL Second Generation instances include:
- Up to 7X throughput and 20X storage capacity of first generation instances
- Less expensive than First Generation for most use cases
- Option to add High Availability failover and read replication
- Configurable backup period and maintenance window
- Proxy support
Because Cloud SQL Second Generation instances are in beta, the following features are not available:
- Service Level Agreement (SLA)
- MySQL 5.5
MySQL 5.6 is supported.
- Google App Engine connectivity
Connectivity is supported for other clients, including Compute Engine, Managed VMs, Container Engine, and your workstation.
- Point-in-time recovery from backups
- Standard Persistent Disk (HDD) support
Solid-state Persistent Disk (SSD) is supported and used by default.
- Automatic scaling of storage capacity
You can increase storage capacity manually with no downtime.
- IPv6 connectivity
IPv4 is fully supported.
If you do not require an SLA, we recommend selecting Cloud SQL Second Generation instances, because they provide more performance at a lower cost for most use cases. First Generation instances remain available for use cases that require a capability that is not yet supported for Second Generation.