Quotas and limits

This page provides information about the Cloud SQL quotas and limits. Quotas are applied per-project; limits are applied to the instance or to the project, depending on the limit.

Checking your quotas

To check the current quotas for resources in your project, go to the Quotas page in the Google Cloud Platform Console.

Increasing your quotas

As your use of GCP expands over time, your quotas can increase accordingly. If you expect a notable upcoming increase in usage, you should make your request a few days in advance to ensure your quotas are adequately sized.

  1. In the Quotas page, select Cloud SQL Admin API in the Services dropdown list.

    If you do not see Cloud SQL Admin API, the Cloud SQL Admin API has not been enabled.

  2. Select the quotas you want to change.

  3. Click Edit quotas.

  4. Fill out your name, email, and phone number and click Next.

  5. Fill in your quota request and click Submit request.

You will receive a response from the Cloud SQL for MySQL team within 48 hours of your request.

How resource quotas are replenished

Daily quotas are replenished daily at midnight Pacific time.

Quotas and resource availability

Resource quotas are the maximum amount of resources you can create for that resource type if those resources are available. Quotas do not guarantee that resources will be available at all times. If a resource is not physically available for your region, you will not be able to create new resources of that type, even if you still have remaining quota in your project.


There are restrictions on some Cloud SQL resources that are not replenished periodically and not shown on the Quotas page in the Google Cloud Platform Console. Some limits can be increased while others cannot.

Configurable limits

Instances per project

By default, you can have up to 40 instances per project per region. If you need more, file a support case to request the increase.

Fixed limits

Cloud SQL for MySQL Second Generation connection limits

Machine type Default concurrent connections1
db-f1-micro 250
db-g1-small 1,000
All other machine types 4,000

1 You can use the max_connections flag to configure connections limits (beta). However, the Cloud SQL team recommends using default connection limits to ensure instance stability.

Cloud SQL for MySQL First Generation connection limits

Incoming connection requests are briefly queued before the connection is established. The queue can accept only 100 incoming connection requests.

Tier Default concurrent connections
D0 - D2 250
D4 500
D8 1,000
D16 2,000
D32 4,000

Cloud SQL storage limits

MySQL First Generation instances MySQL Second Generation instances PostgreSQL and SQL Server instances Notes
250 GB Up to 30,720 GB, depending on machine type Up to 30,720 GB, depending on whether the instance has dedicated or shared vCPUs. See the Instance settings for PostgreSQL or SQL Server. If you have a Silver or higher Google Cloud support package, you can request an increase of up to 500 GB for First Generation instances by using this form.

App Engine Limits

Requests from App Engine applications to Cloud SQL are subject to the following time and connection limits:

  • For apps running in the App Engine standard environment, all database requests must finish within the HTTP request timer, around 60 seconds. For apps running in the flexible environment, all database requests must finish within 60 minutes.
  • Offline requests like cron tasks have a time limit of 10 minutes.
  • Requests to Cloud SQL have limitations based on the scaling type of the App Engine module and how long an instance can remain in memory (residence).
  • Each App Engine instance running in a standard environment cannot have more than 100 concurrent connections to a Cloud SQL instance. For applications written in Java 7, Go 1.6, or PHP 5.5, the limit is 60 concurrent connections.

App Engine applications are also subject to additional App Engine quotas and limits as discussed on the App Engine Quotas page.

หน้านี้มีประโยชน์ไหม โปรดแสดงความคิดเห็น