Cloud SQL FAQ

About

What is Cloud SQL?
Cloud SQL is an easy-to-use service that delivers fully managed SQL databases in the cloud. Cloud SQL provides PostgreSQL, SQL Server, and MySQL databases.
What are the benefits of using Cloud SQL?
Cloud SQL 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 wire protocols, it’s easy to connect from just about any application, anywhere.
Which database versions are available with Cloud SQL? How are updates managed?

For Cloud SQL for MySQL, MySQL instances support MySQL 5.6 and 5.7 (default). Cloud SQL for PostgreSQL supports PostgreSQL 9.6, 10, 11, and 12 (default). Cloud SQL for SQL Server supports SQL Server 2017 Standard (default), SQL Server 2017 Enterprise, SQL Server 2017 Express, and SQL Server 2017 Web. Minor version updates are deployed as they are released, with no further action required on your part. For more information about updates, see Overview of maintenance on Cloud SQL instances.

To see the current version of your instance, go to the Google Cloud Console, click the instance name to open the Instance details page. Or, you can use the gcloud sql instances describe command.

Does Cloud SQL support all database features?
Cloud SQL supports most common features of MySQL or PostgreSQL. For a list of all differences between standard database functionality and what Cloud SQL provides, see Differences between Cloud SQL and standard MySQL functionality and see Differences between Cloud SQL and standard PostgreSQL functionality. Also see SQL Server features unavailable for Cloud SQL.
Are there any size or QPS limits?
There are no queries per second (QPS) limits for Cloud SQL instances. For information about connection, size, and App Engine-specific limits, see Quotas and Limits.
How can I be notified when there are any changes to Cloud SQL?
You can sign up for the google-cloud-sql-announce forum where we post announcements and news about Cloud SQL.
How do I report a bug, request a feature, or ask a question?
You can report bugs and request a feature on our google-cloud-sql-discuss group. You can ask a question in Stack Overflow. For other support options, see the Cloud SQL Support page.
Back to top

Getting Started

What is the best MySQL tool to use for managing my instance?
There are a variety of MySQL tools available for Cloud SQL. For executing simple statements, you can use the MySQL Command-Line Tool. For executing more complicated tasks or to use a richer database development environment, you can try Toad for MySQL or MySQL Workbench. For more information, see Admin and Reporting Tools.
What storage engine should I use?
For MySQL instances, InnoDB is the only storage engine supported.

If you have a mysqldump file where all your tables are in MyISAM format, you can convert them to InnoDB format by piping the file through a sed script:

mysqldump --databases [DATABASE_NAME] \
-h [INSTANCE_IP] -u [USERNAME] -p [PASSWORD] \
--hex-blob --default-character-set=utf8mb4 | sed 's/ENGINE=MyISAM/ENGINE=InnoDB/g' > [DATABASE_FILE].sql

Warning: You should not do this if your mysqldump file contains the mysql schema. Those files must remain in MyISAM.

Why does my new instance with no data show disk space used?
Cloud SQL and the database both use some space for system files and metadata when your instance is created.
Back to top

Data Storage and Replication

Where is my data stored?

MySQL instances: Instance data is stored in the region where the instance resides. By default, Cloud SQL stores backup data in two regions for redundancy. If there are two regions in a continent, the backup data remains on the same continent. Because there is only one region in Australia, backup data from the Sydney region is stored in a location in Asia. For the São Paulo region, backup data is stored in a US-based location.

PostgreSQL instances: Instance data is stored in the region where the instance resides. By default, Cloud SQL stores backup data in two regions for redundancy. If there are two regions in a continent, the backup data remains on the same continent. Because there is only one region in Australia, backup data from the Sydney region is stored in a location in Asia. For the São Paulo region, backup data is stored in a US-based location.

What is a zone?

A zone is an independent entity in a specific geographical location where you can run your resources. For example, a zone named us-central1-a indicates a location in the central United States.

For MySQL instances, fault tolerance across zones can be achieved by configuring the instance for high availability. The high availability configuration is strongly recommended for all production instances.

For more information about zones, see Zone Resources in the Compute Engine documentation.

What are the limits on storage?
For information on storage limits, see Quotas and Limits.
How is my data replicated?

MySQL instances: MySQL instances provide a high availability configuration and MySQL read replicas. MySQL read replicas use asynchronous replication.

PostgreSQL instances provide a high availability configuration and read replicas.

How does Cloud SQL failover work?

For information about failover, see Overview of the High Availability Configuration.

Is my data encrypted?
Cloud SQL customer data is encrypted when stored in database tables, temporary files, and backups. External connections can be encrypted by using SSL, or by using the Cloud SQL Proxy.
How is encryption managed for data at rest?

Your data is encrypted using the 256-bit Advanced Encryption Standard (AES-256), or better, with symmetric keys: that is, the same key is used to encrypt the data when it is stored, and to decrypt it when it is used. These data keys are themselves encrypted using a master key stored in a secure keystore, and changed regularly.

For more details, see Encryption at Rest in Google Cloud.

How is encryption managed for data in transit?

Google encrypts and authenticates all data in transit at one or more network layers when data moves outside physical boundaries not controlled by Google or on behalf of Google. Data in transit inside a physical boundary controlled by or on behalf of Google is generally authenticated but might not be encrypted by default. You can choose which additional security measures to apply based on your threat model. For example, you can configure SSL for intra-zone connections to Cloud SQL.

For more details, see Encryption in Transit in Google Cloud.

What kind of read replicas can I create?

For more information about read replicas, including use cases for each type, see Replication Options.

How can I tell if an instance is a read replica?
You can use the Google Cloud Console to see all of your Cloud SQL instances, and whether an instance is a master or read replica instance. You can also use the Cloud SDK to check whether an instance is a master or read replica. For more information, see Checking replication status.
Does Cloud SQL provide load balancing for requests to read replicas?
Cloud SQL does not automatically provide or configure load balancing. You can use connection pooling to distribute read requests between read replicas by switching between multiple connection endpoints.
Back to top

Backup and Recovery

How do I recover an instance?

To restore to a backup you can use the Google Cloud Console or the gcloud command-line tool. For more details, see Restoring an Instance.

To restore a MySQL instance to a specific point in time, you use a point-in-time recovery. For more information, see Performing a Point-in-Time Recovery.

How much do backups cost?

MySQL instances: The most recent 7 automated backups, and all on-demand backups, are retained. They are charged at the backup storage rate. Binary logs use storage space (not backup space), and are charged as storage.

PostgreSQL instances: The most recent 7 automated backups, and all on-demand backups, are retained. They are charged at the backup storage rate.

For more information about instance storage pricing and instance rates, see Pricing.

How does point-in-time recovery impact performance?
Point-in-time recovery requires that you enable binary logging. This means that every update to your database is written to an independent log, which involves a small reduction in write performance. Performance of read operations are unaffected by binary logging, regardless of the size of the binary log files.
Back to top

Managing Your Instances

Which actions might cause Cloud SQL instances to restart?
Cloud SQL instances might be restarted when you or Cloud SQL takes the following actions:
  • Update
  • Create
  • Promote replica
  • Maintenance
  • Recreate replica
  • Failover
  • Restart
  • Restore instance from backup
  • Enable high availability on an existing instance (this is an update to the instance)
  • Add a database flag that requires a restart
See How long are instances shut down during restart?.
How long are instances shut down during restart?

When instances are restarted, the majority of them are shut down for one to two minutes. Before the instance is shut down, all connections are killed and current work is flushed from disk. For instances with a large load, this process takes longer, and it might look like the instance is stuck. In these cases, it might take up to an hour for the instance to shut down and restart.

Can I make my database larger or smaller?

MySQL and PostgreSQL instances: You can increase the amount of storage available to your instance at any time without incurring downtime. You cannot decrease the size of the storage of your instance. You can also configure your instance to automatically increase its storage capacity when space is running low. Learn more.

Can I upgrade and downgrade vCPUs?

Yes, you can change the number of vCPUs that you use on your instance. You can increase or decrease the number of cores you use as many times as you want. It typically takes less than five minutes of downtime to change the number of vCPUs.

Do I need to use the Google Cloud Console to manage Cloud SQL?
No. All management tasks that can be done via the Console can also be done programmatically using the Cloud SQL Admin API, or scripted using the gcloud command-line tool.
How can I reclaim the space from a dropped table?
When you drop a table from a database and then check the Google Cloud Console, you might see that the space freed by dropping the tables is not reflected in the reported Storage Used of the instance. Instances running MySQL 5.5 have the innodb_file_per_table flag set to OFF by default; InnoDB never shrinks its default tablespace. To reclaim space for this configuration, create a new instance from the smaller database, or change the value of the innodb_file_per_table flag to ON. For information about changing database flags, see Configuring Database Flags.
How can I reclaim the space used by temporary files?
Temporary files can grow when SQL queries create many temporary tables. To reclaim the space used by temporary tables, you need to restart the database. Note that restarting the database does not reduce the provisioned disk space resulting from the growth of temporary files.
How can I track changes to data?
To track changes to data, enable binary logging for your instance. Tracking changes to data can help you recover from accidental data loss. In the event of accidental data loss such as from a DROP DATABASE command, you can restore up to the binary log coordinates just before the data loss event. For more information, see point-in-time recovery. Point-in-time recovery and binary logging are not yet available for PostgreSQL instances.
Can I import or export a specific database?
Yes. For MySQL instances, you can import and export either a single database or multiple databases. For PostgreSQL instances, you can only import or export a specific database.
Can I import or export a CSV file?
Do I need a Cloud Storage account to import or export data to an instance?
Cloud SQL supports importing and exporting databases (compressed or uncompressed SQL dump files) and CSV files using a Cloud Storage bucket. To import or export using a Cloud Storage bucket, you need to either sign up for a Google Cloud account and create a bucket, or have access to a Cloud Storage bucket in another account. For more information, see Importing Data or Exporting Data.
What does ERROR_RDBMS mean on an import operation?
This error occurs if MySQL returns an error during a data import operation. Common causes include invalid syntax, using a database or table that has not been defined, and attempting to run MySQL statements that require the SUPER privilege.
If I delete my instance, can I reuse the instance name?
Yes, but not right away. The instance name is unavailable for up to a week before it can be reused.
What is the cloudsqladmin database user?
Every Cloud SQL instance includes a database user called cloudsqladmin. You may notice this user if you do a SHOW GRANTS FOR cloudsqladmin@localhost. On some instances this will also show up in the system user table. This user account is used by automated processes that need to access the data in your instance (for example, backing up your instance or performing an import or export).
How can I use GRANT ALL?
Cloud SQL does not support SUPER privileges, which means that GRANT ALL PRIVILEGES statements will not work. As an alternative, you can use GRANT ALL ON `%`.*.
How can I access transaction logs for my instances?
For MySQL instances, if you enable binary logging for your instance (see Enabling binary logging) and configure an IP address for your instance (see Configuring access for IP connections), then you can use the standard MySQL mysqlbinlog utility to examine the transaction logs for the instance.
What level of transaction isolation does Cloud SQL provide?

MySQL instances: Cloud SQL provides REPEATABLE READ transaction isolation. You can change the transaction isolation level for the current session, but usually the default value is preferred. For more information, see Transaction Isolation Levels in the MySQL documentation.

PostgreSQL instances: Cloud SQL provides Read committed transaction isolation. You can change the transaction isolation level for a specific transaction, but usually the default value is preferred. For more information, see Transaction Isolation in the PostgreSQL documentation.

Back to top

Pricing and Billing

How can I try out Cloud SQL?
The smallest instance is the db-f1-micro. You can use it to try out the service. Note that shared core instances are not covered by the SLA.
How many instances can I create in a project?
For information about the instance limit, see Quotas and Limits.
What size database instance do I need? How much RAM?
In general, you can increase the performance of your database by choosing a larger instance with more RAM and CPU. This increases the performance of many queries that involve large amounts of computation, such as those involving joins, ORDER BYs, or GROUPing, though the performance of updates affecting single rows will not be much affected. For more information about instance sizes and pricing, see the pricing page.
How is use of my instance calculated?

MySQL and PostgreSQL instances: You are charged per minute for the time that your instance is on.

How is storage calculated?

MySQL and PostgreSQL instances: Storage is calculated based on the amount of storage you have provisioned for your instance. Storage for backups is charged by how much space your backups are using. Storage is charged whether your instance is on or off.

How can I see how much I will be charged?
The Billing tab of the Google Cloud Console shows you the charges your instances have incurred since the last bill was issued.
What happens when my instance reaches the allowed size?

MySQL and PostgreSQL instances: If your instance reaches the provisioned storage size, and you do not have automatic storage increase enabled or it has reached its configured limit, future writes to the database are disallowed until you increase the storage size. Increasing the storage size does not require an instance restart or downtime.

Why is my instance suspended?
This is probably due to an issue with your Google Cloud account. You can determine your billing status by filing a Billing Support Request. After the billing issue is resolved, the instance returns to runnable status within a few hours. Note that suspended MySQL instances are deleted after 90 days.
Why was my instance deleted?
PostgreSQL and MySQL instances that are suspended for 90 days are deleted. This applies to instances with a state of SUSPENDED. Instances that are stopped, with a state of RUNNABLE, are not deleted.
How can I cancel my Cloud SQL account?
You can deactivate Cloud SQL for a project by visiting the Google Cloud Console, selecting the project, selecting the API service to open the API Dashboard. Find the Cloud SQL API and click Disable for that API.
How do I disable billing?
You can disable billing by clicking Disable billing in the Google Cloud Console Billing & settings pane for a project. If you disable billing, you also disable the Cloud SQL service. Make sure you really want to disable the Cloud SQL service before you disable billing.

After you disable billing, you will receive one last bill for charges that occurred between the beginning of the billing cycle and when you cancelled.

Back to top

Using Cloud SQL with App Engine

Can I connect from App Engine to a MySQL instance?
You can connect from an App Engine application to a MySQL instance, whether the application is running in the standard or the flexible environment. For more information, see Connecting from App Engine standard environment, or Connecting from App Engine flexible environment.
Can I connect from App Engine to a PostgreSQL instance?
You can connect from an App Engine application to a PostgreSQL instance, depending on the environment and language you are using. For more information, see Connecting from App Engine standard environment, or Connecting from App Engine flexible environment.
Can my App Engine in the US access my Cloud SQL instance in the EU (and vice versa)?

If you are connecting to a MySQL instance, your App Engine application does not need to be in the same region, and it can be running in either the standard or the flexible environment. However, a larger distance between your Cloud SQL instance and your App Engine application causes greater latency for connections to the database.

If you are connecting to a PostgreSQL instance, your App Engine application does not need to be in the same region. However, a larger distance between your Cloud SQL instance and your App Engine application causes greater latency for connections to the database.

Which Google Cloud database service is right for me?
This depends on the requirements of your application. Google Cloud offers a number of services for storing and retrieving your data. For more information, see Storage Options.
Do I need to install a local database server to use the App Engine Development Server?
No. You can configure App Engine to use either Cloud SQL or a locally installed database server when running on the development server.
What languages can I use to access my instance?
App Engine supports several languages that you can use to connect to your instances. For more information, see Connecting from App Engine standard environment, or Connecting from App Engine flexible environment.

If you are not using App Engine, you can use any language that has an associated connector or API. For a list of supported languages, see the Connectors and APIs chapter in the MySQL Reference Manual.

Can I use Django with Cloud SQL?
Yes, Cloud SQL is compatible with Django. See Getting Started with Django.
Which placeholders can I use in my Python query string?
Python users can only use the %s format code in parameter substitution. Therefore, the following statement is invalid: cursor.execute('INSERT INTO entries (guestAge) VALUES (%d)', (age)).
How should I manage connections?

Managing your database connections effectively is an important aspect of database application development, including using connection pooling and exponential backoff. For examples of how to employ these techniques in a variety of languages and frameworks, see Managing database connections.

To learn more about instance connection limits, see Quotas and Limits.

What does a SQLException with message of "Invalid connection ID" mean?
It means that the connection is no longer open on the server and should be discarded by the client.  You do not need to call 'close' on these connections; they are already closed.
Can I access my Cloud SQL instance programmatically outside of App Engine?
Yes. You can access Cloud SQL instances programmatically from external applications using any supported language. See Connecting from External Applications.
Back to top