Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Cloud SQL Usage and SKUs pricing issue

Snapshot of the billing reportSnapshot of the billing report
Hi Team,
I was using Cloud SQL, and I was charged against 5.2 gigibyte hour and I am struggling to find out that how the usage is calculated?
  1. I have created only 2 tables in the cloud SQL with 30 rows and 8 columns.
  2. From the created 2 tables, I have made a view such that its results can be exported into looker studio.
  3. I was charged for basically 3 SKUs majorly i.e. Cloud SQL for MySQL: Regional - RAM in Americas, Cloud SQL for MySQL: Regional - vCPU in Americas, Cloud SQL for MySQL: Regional - Standard storage in Americas.

Can someone please help me with the calculation of usage that resulted in charges and possibly about the SKUs against which I am charged?

I tried contacting billing team for this issue but they only helped me with the breakup of the charges, but I want to understand why the usage is so high and why I was charged against multiple SKUs?

0 1 1,912
1 REPLY 1

The Google Cloud SQL pricing model is based on several components. These include the following:

  1. CPU and memory usage: 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. The pricing for CPUs and memory depends on the region where your instance is located. Read replicas and failover replicas are charged at the same rate as standalone instances​.

  2. Storage and networking: Storage and networking prices also depend on the region where the instance is located. Committed use discounts do not apply to storage or network prices​.

  3. 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. For example, between regions within North America, the price is $0.12/GB. Internet egress is $0.19/GB if not using Cloud Interconnect​.

  4. Licensing: SQL Server also has a licensing component based on the chosen edition. For example, the Enterprise edition is $0.47 per core hour, the Standard edition is $0.13 per core hour, and the Web edition is $0.01134 per core hour. The Express edition is free. Note that a core license needs to be assigned to each virtual CPU on your instance, with a minimum of four cores 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 more details please see https://cloud.google.com/sql/docs/sqlserver/pricing

In terms of billing, Google Cloud SQL instances are billed as long as they are running, not on a pay-per-request basis. The storage that you use will also be billed, and it can automatically grow according to usage. Note that the storage cannot be reduced, even if you delete data in the database. It's important to note that the price for a Cloud SQL instance can be about twice the price of a similar compute engine instance. This higher price includes management of the SQL instance, such as updates/patches, security/network access management, snapshot and restoration management, high availability assurance, database parameter tuning, storage management, and setup of replicas​​.

These prices are as of the date of the last available information and may vary depending on the region and currency.

Please note that to get the exact cost for your specific use-case, you would need to use the Google Cloud Pricing Calculator with the specific parameters of your workload.