Compute Engine Cloud SQL BigQuery

Cloud SQL costs

Resource Details

Estimation

ItemAmount
Add a Cloud SQL configuration to see an estimate.
Estimated Total
$0.00 / mo

Optimize Your GCP Spend

Connect your GCP project to Economize and discover savings opportunities up to 30% instantly.

Get started for free

HOW TO USE THIS CALCULATOR

Estimate your GCP bill in three steps

1

Configure your workloads

Select machine families (e.g. N1, N2, C2) or database configs and choose your GCP region. Rates vary by region — us-central1 is typically the cheapest baseline.

2

Set usage and quantity

Enter how many days per month each instance runs and how many instances you need. A 24/7 workload is 730 hours per month; dev environments often run far less.

3

Compare and decide

Evaluate Committed Use Discounts (1-yr or 3-yr CUDs) against On-Demand pricing to see instant savings and totals updated live.

PRICING MODEL

How Cloud SQL pricing works

Cloud SQL charges are assembled from four independent parts: the compute allocated to the instance, the storage it is provisioned with, backup retention, and network egress. Compute is billed on vCPU and memory, either as a shared-core instance for light workloads or as a dedicated-core instance sized to your throughput. Because storage is billed on what is provisioned rather than what is used, and Cloud SQL can grow storage automatically, an instance can quietly become more expensive over time.

High availability is the single largest multiplier on a Cloud SQL bill. Enabling it creates a synchronous standby in a second zone and roughly doubles the compute and storage cost of the instance without doubling query throughput. SQL Server adds per-core licensing on top of the machine rate, which varies by edition and often exceeds the hardware charge. Read replicas are billed as separate instances at full rate.

What drives your Cloud SQL bill

Database engine

MySQL and PostgreSQL are billed on infrastructure alone. SQL Server adds a per-core licence charge that differs between Web, Standard, and Enterprise editions and frequently costs more than the underlying machine.

Instance size

Shared-core tiers suit development and low-traffic services. Dedicated-core instances bill vCPU and memory separately, so tuning for memory raises cost independently of CPU.

Storage type and size

SSD is the default and costs more per GB than HDD while delivering far better IOPS. You pay for provisioned capacity, and automatic storage increase never shrinks the allocation back down.

High availability

A regional HA configuration maintains a standby in another zone and approximately doubles compute and storage charges. It buys failover protection, not additional read capacity.

Backups and egress

Automated backups and retained point-in-time recovery logs are charged per GB. Cross-region replicas and traffic leaving Google Cloud add network egress on top of the instance cost.

Cloud SQL pricing questions

How accurate is this Cloud SQL pricing calculator?
Rates are based on published Google Cloud SQL pricing for each region and are refreshed regularly. Your actual invoice may differ once backup retention, point-in-time recovery logs, read replicas, and network egress are included, since each is billed separately from the instance itself.
How much does high availability add to a Cloud SQL bill?
Why does SQL Server cost more than MySQL or PostgreSQL?
Does Cloud SQL storage cost shrink if my database gets smaller?
Are committed use discounts available for Cloud SQL?
How are read replicas billed?