Pricing for Cloud SQL depends on your instance type:
SQL Server pricing
Cloud SQL for SQL Server is composed of the following charges:
CPU and memory pricing
For dedicated-core instances, you choose the number of CPUs and the amount of memory you want, up to 96 CPUs and 416 GB of memory. Pricing for CPUs and memory depends on the region where your instance is located. Select your region in the dropdown on the pricing table.
HA prices are applied for instances configured for high availability, also called regional instances. Learn more.
Storage and networking pricing
SQL server storage and networking prices depend on the region where the instance is located. Select your region in the dropdown on the pricing table.
HA prices are applied for instances configured for high availability, also called regional instances. Learn more.
Network Egress Pricing
When network traffic leaves a Cloud SQL instance, the charge applied depends on the destination of the traffic, and in some cases, whether a partner is involved.
Internet egress is network traffic leaving a Cloud SQL instance to a client that is not a Google product, such as using a local server to read data from Cloud SQL.
| Destination | Price |
|---|---|
| Compute Engine instances | Within the same region: free Between regions within North America: $0.12/GB Between regions outside of North America: $0.12/GB |
| Google Products (except Compute Engine) |
Intra-continental: free Inter-continental: $0.12/GB |
| Internet egress using Cloud Interconnect | $0.05/GB |
| Internet egress (not using Cloud Interconnect) | $0.19/GB |
Licensing
In addition to instance and resource pricing, SQL Server also has a licensing component based on the chosen edition. High availability, or regional instances, will only incur the cost for a single license for the active resource. Learn more about instance creation and the various editions here.
| License | Price per Core Hour |
|---|---|
| Enterprise | $0.47 |
| Standard | $0.13 |
| Web | $0.01134 |
| Express | $0 |
Microsoft SQL Server licensing requires a core license to be assigned to each virtual CPU on your instance, with a four core minimum for each instance. Instances with fewer than 4 vCPUs will be charged for SQL Server at 4 times the license rate to comply with these requirements. For instances with 4 or more vCPUs, you will be charged for the number of SQL Server licenses that is equal to the number of vCPUs.
SQL Server instances are charged a 10 minute minimum for licenses. After 10 minutes, SQL Server licenses are charged in 1 minute increments.
MySQL pricing
Instance Pricing
Instance pricing for MySQL is charged for every second that the instance is running
(the activation policy is set to ALWAYS). Cloud SQL uses seconds as the time
unit multiplier for usage. This means that each second of usage counts toward a full billable
minute. Milliseconds of usage are rounded to the nearest second. If usage is under half a second,
(499ms or less), it rounds down to zero and does not count toward billable usage.
For example:
- If you use an instance for 499ms, you are not billed for that second.
- If you use an instance for 500ms or 1.49 seconds, in both cases, you are billed for 1 second.
- If you use an instance for 1.5 seconds or 2.49 seconds, in both cases you are billed for 2 seconds.
The charge for usage also changes depending on the machine type you choose for the instance, and the region where the instance is located. Zones have no impact on the price.
In the following table:
- Select your region from the dropdown menu to see the price for that region
- Use the slider to choose Monthly or Hourly pricing
- Find the machine type you want to use to view pricing details
Read replicas and failover replicas are charged at the same rate as stand-alone instances.
*Shared CPU machine types (db-f1-micro and db-g1-small) are not covered by the Cloud SQL SLA.
Storage and Networking Pricing
Storage and networking prices for MySQL instances depend on the region where the instance is located. Select your region from the dropdown on the pricing table.
Network Egress Pricing
When network traffic leaves a Cloud SQL instance, the charge applied depends on the destination of the traffic, and in some cases, whether a partner is involved.
Internet egress is network traffic leaving a Cloud SQL instance to a client that is not a Google product, such as using a local server to read data from Cloud SQL.
| Destination | Price |
|---|---|
| Compute Engine instances and Cloud SQL cross-region replicas | Within the same region: free Between regions within North America: $0.12/GB Between regions outside of North America: $0.12/GB |
| Google Products (except Compute Engine and traffic to Cloud SQL cross-region replicas) |
Intra-continental: free Inter-continental: $0.12/GB |
| Internet egress using Cloud Interconnect | $0.05/GB |
| Internet egress (not using Cloud Interconnect) | $0.19/GB |
MySQL pricing examples
You can use the Google Cloud Pricing Calculator to get pricing estimates for your Cloud SQL instances. Here are a few example calculations:
| Use case | Configuration details | Monthly cost | Pricing Calculator |
|---|---|---|---|
| Test instance |
|
$9 | Pricing example |
| Test instance, stopped when not in use |
|
$3 | Pricing example |
| High-performance production database |
|
$7,670 | Pricing example |
PostgreSQL pricing
Cloud SQL for PostgreSQL pricing is composed of the following charges:
Instance pricing
Instance pricing for Cloud SQL for PostgreSQL applies only to shared-core instances. Dedicated-core instances, which can have up to 96 vCPUs and 416 GB of memory, are charged by the number of cores and amount of memory they have. Read replicas are charged at the same rate as stand-alone instances.
Instance pricing depends on the region where the instance is located. Select your region from the dropdown on the pricing table.
HA prices are applied for instances configured for high availability, also called regional instances. Learn more.
*Shared CPU machine types (db-f1-micro and db-g1-small) are not covered by the Cloud SQL SLA.
CPU and memory pricing
For dedicated-core instances, you choose the number of CPUs and the amount of memory you want, up to 96 CPUs and 416 GB of memory. Pricing for CPUs and memory depends on the region where your instance is located. Select your region in the dropdown on the pricing table.
HA prices are applied for instances configured for high availability, also called regional instances. Learn more.
Storage and networking pricing
PostgreSQL storage and networking prices depend on the region where the instance is located. Select your region in the dropdown on the pricing table.
HA prices are applied for instances configured for high availability, also called regional instances. Learn more.
Network Egress Pricing
When network traffic leaves a Cloud SQL instance, the charge applied depends on the destination of the traffic, and in some cases, whether a partner is involved.
Internet egress is network traffic leaving a Cloud SQL instance to a client that is not a Google product, such as using a local server to read data from Cloud SQL.
| Destination | Price |
|---|---|
| Compute Engine instances and Cloud SQL cross-region replicas | Within the same region: free Between regions within North America: $0.12/GB Between regions outside of North America: $0.12/GB |
| Google Products (except Compute Engine and traffic to Cloud SQL cross-region replicas) |
Intra-continental: free Inter-continental: $0.12/GB |
| Internet egress using Cloud Interconnect | $0.05/GB |
| Internet egress (not using Cloud Interconnect) | $0.19/GB |
PostgreSQL instance pricing examples
You can use the Google Cloud Pricing Calculator to get pricing estimates for your Cloud SQL instances. Here are a few example calculations:
| Use case | Configuration details | Monthly cost | Pricing Calculator |
|---|---|---|---|
| Test instance |
|
$9 | Pricing example |
| Test instance, stopped when not in use |
|
$3 | Pricing example |
| High-performance production database |
|
$7,613 | Pricing example |
What's next?
- Refer to the Pricing Overview documentation.
- Try the Pricing Calculator.
- Learn more about instance settings.
- Learn more about the high availability configuration.