Check Cloud SQL compute, storage, backup and network charges
On this page
This check is due for a source refresh. Confirm the current documentation before you rely on provider-specific details.
Review one invoice month before changing Cloud SQL capacity or backups, or you may cut the wrong cost. For MySQL enhanced backups, include the central backup project in scope because vault-stored backup costs can sit outside the instance project.
What you need first
- Tool
- BigQuery is Google's analysis service for exported Cloud Billing tables. Start with an existing detailed table named gcp_billing_export_resource_v1_<BILLING_ACCOUNT_ID>, or ask for a read-only result scoped to Cloud SQL and one invoice month.
- Access
- Ask an authorized billing-data colleague for read-only detailed billing results for the billing account, instance projects, backup project, and invoice month. Ask the Cloud SQL owner to confirm each MySQL backup option and project.
- If you do not use that tool
- Send the billing account, instance projects, any backup project, and invoice month to an authorized billing-data colleague. Request the original detailed rows scoped to those projects and Cloud SQL resources, the invoice.month value, and any export gaps. Ask the Cloud SQL owner to confirm the enhanced-backup project.
Why this is worth a look
Skipping the invoice review can misidentify the cost driver. Cloud SQL pricing includes provisioned storage billed per GiB per month, selected CPUs, selected memory, hosting location, outgoing network traffic, and assigned or used IP addresses.
Skipping the backup-project review can omit enhanced-backup cost. Google states that enhanced-backup cost is based on the total backup size stored in the backup vault, which may be managed across projects.
Run this check
CHECKLISTUse an existing BigQuery detailed export or an authorized colleague's result to review one invoice month without changing billing tables, instances, or backups.
READ-ONLY CHECKLIST
Set the scope
[ ] Record billing account: __________
[ ] Record Cloud SQL instance projects: __________
[ ] Record any MySQL enhanced-backup project: __________
[ ] Record invoice month (YYYYMM): __________
[ ] Identify the detailed table: gcp_billing_export_resource_v1_<BILLING_ACCOUNT_ID>
[ ] If you cannot read the export, ask an authorized billing-data colleague for rows already scoped to Cloud SQL and these projects.
Review the invoice month
[ ] Select the period using invoice.month, not a usage-date window.
[ ] Confirm the requested period is available. Record any period when detailed export was disabled and any recent-data delay.
[ ] Retain the original rows and the fields your export result provides. Do not invent field names or classify rows from a service label alone.
[ ] Request or record any billing modification or adjustment as a separate line item when it appears in the result.
[ ] Group rows only when the original billing information supports the grouping. Keep unclear rows separate.
Include MySQL backups
[ ] Ask the Cloud SQL owner to confirm standard or enhanced backups for each instance.
[ ] For standard backups, include the instance project because standard backups are stored there.
[ ] For enhanced backups, include the central backup project and the relevant backup costs returned for that scope. Do not assume a billing label or row category that the export result does not identify.
[ ] Record the backup vault's total stored backup size, reported unit, and observation time when available; do not use it as a month's invoice total.
Compare usage context
[ ] In the Google Cloud console, open Cloud SQL Instances and click the instance name to open Overview. Select the needed metric from the Chart list.
[ ] Record the chart window and units for storage, CPU, and memory observations.
[ ] Keep chart storage usage in GB separate from provisioned storage priced in GiB per month.
Return the original billing rows, scope, invoice month, supported groupings, unresolved rows, backup scope, and known data gaps. Make no configuration changes.How to confirm it
- 01
Choose one invoice month
Record the billing account, instance projects, any enhanced-backup project, and invoice month in YYYYMM format. Ask for detailed billing results selected by invoice.month, not a usage-date window, because late-reported usage and adjustments can appear on a later invoice.
- 02
Request scoped billing rows
Ask the billing-data colleague to return original detailed rows for Cloud SQL resources and the listed projects. Do not rely on an unspecified label or an assumed field name. Keep any row that cannot be supported as Cloud SQL separate and unresolved.
- 03
Include MySQL backup scope
Ask the Cloud SQL owner to confirm each MySQL backup option. Include the instance project for standard backups. For enhanced backups, include the central backup project and the relevant backup costs returned for that scope, without assuming a specific billing label.
- 04
Compare charts without replacing billing
Open the instance Overview page and record storage, CPU, and memory chart windows and units. Keep these observations separate from invoice charges: Cloud SQL storage pricing uses provisioned GiB per month, while the monitoring chart reports storage usage in GB.
Before making changes
Assume the project list is complete only after the Cloud SQL owner confirms backup ownership. Detailed export availability depends on enablement, dataset configuration, and reporting timing; disabled periods and recent data may be missing. Backup and monitoring instructions here apply to MySQL. A current chart or vault-size reading does not reconstruct a month's invoice, and this review does not establish that reducing capacity or retention is safe.