Cloud SQL pricing
This page contains information about pricing for Cloud SQL.
Cloud SQL offers two editions, Enterprise and Enterprise Plus. These editions provide different levels of availability, performance and data protection. The pricing for the vCPUs and memory for each edition varies. Cloud SQL Enterprise edition and Cloud SQL Enterprise Plus edition are supported by Cloud SQL for MySQL, Cloud SQL for PostgreSQL, and Cloud SQL for SQL Server.
Extended support pricing
Extended support pricing applies to Cloud SQL instances that are running major versions in extended support. Refer to the Database version policies documentation for the extended support timelines of Cloud SQL major versions.
Extended support is priced per vCPU per hour and charged for every second that the instance is running. Extended support is charged in addition to regular instance pricing. For more details, see Billing on partial seconds. Pricing depends on the region where your instance is located. Select your region in the dropdown on the pricing table.
Read replicas are charged at the same rate as stand-alone instances.
HA prices are applied for instances configured for high availability, also called regional instances. Learn more about high availability.
In the following table, select your region from the dropdown menu to see the price for that region.
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 624 GB of memory. For Cloud SQL Enterprise Plus edition instances, you can choose from Performance-optimized machines (up to 128 CPUs and 864 GB of memory) and Memory-optimized machines (up to 16 CPUs and 512 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.
Read replicas and failover replicas are charged at the same rate as stand-alone instances.
HA prices are applied for instances configured for high availability, also called regional instances. Learn more about high availability.
Cloud SQL also offers committed use discounts (CUDs) that provide deeply discounted prices in exchange for your commitment to continuously use database instances in a particular region for a one- or three-year term. In the pricing tables on this page, the prices for CUDs are listed as commitments. For more information about these commitments, see Committed use discounts.
In the following tables:
- Select your region from the dropdown menu to see the price for that region
- Use the slider to choose Monthly or Hourly pricing
- Compare pricing between per use, 1-year, and 3-year commitments
Enterprise edition
Enterprise Plus edition
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 about high availability.
In the following table, select your region from the dropdown menu to see the price for that region.
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. High availability, or regional instances, will only incur the cost for a single license for the active resource.
You can learn more about instance creation and the various editionshere.
| 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.
Disabling simultaneous multithreading (SMT) reduces the number of virtual CPUs (vCPUs) per core from 2 to 1, which in turn might reduce your SQL Server licensing costs. Disabling SMT doesn't change the compute engine price for SQL Server. You are billed for the number of vCPUs defined in the SQL Server CPU configuration. The following examples show how disabling SMT affects your billing:| User | SMT: enabled or disabled | Number of vCPUs on the instance | Number of vCPUs the SQL Server licensing fees are calculated for | Number of vCPUs the compute charges are calculated for |
|---|---|---|---|---|
| User1 | Enabled | 8 | 8 | 8 |
| User2 | Disabled | 8 | 4 | 8 |
| User3 | Disabled | 6 | 4 | 6 |
SQL Server instance licenses are charged a 1 minute minimum. After 1 minute, SQL Server instance licenses are charged in 1 second increments.
Cloud DNS pricing
With Cloud DNS pricing, the charge is per zone per month (regardless of whether you use your zone), and you also pay for queries against your zones. For more information, see Cloud DNS pricing.What's next
- Learn more about Cloud SQL Enterprise Plus edition.
- Refer to the Pricing Overview documentation.
- Visit the pricing examples page to see how you can calculate your potential costs.
- Try the Pricing Calculator.
- Learn more about instance settings.
- Learn more about the high availability configuration.