> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/cloud-service-intelligence/cloud-service-intelligence/gcp/database/cloud-sql.md). # Cloud SQL ## GCP Cloud SQL — commitment brief > **Data sourced**: March 2026. Verify current figures at the [Google Cloud Pricing Calculator](https://cloud.google.com/products/calculator). ### Coverage summary Cloud SQL supports spend-based committed use discounts (CUDs) that apply to CPU and memory costs for database instances across MySQL, PostgreSQL, and SQL Server. A 1-yr commitment delivers a 25% discount and a 3-yr commitment delivers a 52% discount over on-demand pricing. CUDs are scoped to a region within a billing account and apply automatically across all eligible Cloud SQL instance usage in that region. **What is covered**: Cloud SQL database instance vCPU and memory usage (standard and high-memory tiers) for MySQL, PostgreSQL, and SQL Server across all regions where your commitment is purchased. **What is not covered**: Storage costs (SSD and HDD), backup storage, IP address charges, outbound data transfer, and database licensing fees (e.g., SQL Server license). Shared-core machine types (db-f1-micro, db-g1-small) are excluded from CUDs. ### CUD types > Cloud SQL offers spend-based CUDs only. There is no resource-based CUD for Cloud SQL — you commit to a minimum hourly dollar spend on Cloud SQL instance compute in a region rather than to a specific number of vCPUs or GiB of memory. This makes the commitment flexible across instance types and sizes within the region. Both 1-yr (25% off) and 3-yr (52% off) terms are available. ### Machine type / SKU coverage | Machine Type / SKU | Spend CUD | 1-yr discount | 3-yr discount | Notes | | ---------------------------------------------------------- | --------- | ------------- | ------------- | ------------------------------- | | Standard tier (db-n1-standard, db-custom, db-perf) — MySQL | ✅ Yes | \~25% | \~52% | Covers CPU and memory charges | | Standard tier — PostgreSQL | ✅ Yes | \~25% | \~52% | Same rates as MySQL | | Standard tier — SQL Server | ✅ Yes | \~25% | \~52% | SQL Server license fee excluded | | High-memory tier (db-n1-highmem, db-highmem) — MySQL | ✅ Yes | \~25% | \~52% | | | High-memory tier — PostgreSQL | ✅ Yes | \~25% | \~52% | | | High-memory tier — SQL Server | ✅ Yes | \~25% | \~52% | SQL Server license fee excluded | | Shared-core (db-f1-micro, db-g1-small) | ❌ No | — | — | Explicitly excluded from CUDs | | Storage (SSD / HDD) | ❌ No | — | — | Not covered by any CUD | | Backup storage | ❌ No | — | — | Not covered | | IP address fees | ❌ No | — | — | Not covered | ## Regional availability Available in all commercial GCP regions. Google's documentation states that "Cloud SQL is available in all Google Cloud regions and is offered in upcoming regional launches at the time of launch." Spend-based CUDs are purchased per region and apply automatically to all eligible Cloud SQL instance compute (MySQL, PostgreSQL, and SQL Server) in that region within the billing account. ⚠️ CUD availability varies by machine type and region. Always verify at [GCP regions and zones](https://cloud.google.com/compute/docs/regions-zones) before purchasing. ### Archera Google Cloud SQL is within Archera's commitment management scope. Archera can automate spend-based CUD purchase for Cloud SQL, monitor utilization across MySQL, PostgreSQL, and SQL Server instances by region, and wrap commitments in a GRI/GSP — eliminating downside risk on over-commitment while preserving the full 25–52% discount. *** **Sources** * [Committed use discounts — Cloud SQL](https://cloud.google.com/sql/cud) * [Committed use discounts — Cloud SQL for MySQL](https://cloud.google.com/sql/docs/mysql/cud) * [Committed use discounts — Cloud SQL for PostgreSQL](https://cloud.google.com/sql/docs/postgres/cud) * [Committed use discounts — Cloud SQL for SQL Server](https://cloud.google.com/sql/docs/sqlserver/cud) * [Cloud SQL database instances now discounted (blog)](https://cloud.google.com/blog/products/databases/cloud-sql-database-instances-now-discounted) * [Cloud SQL pricing](https://cloud.google.com/sql/pricing) ⚠️ Discount percentages are approximate and region-dependent. Always verify with the [Google Cloud Pricing Calculator](https://cloud.google.com/products/calculator). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.archera.ai/help-center/cloud-service-intelligence/cloud-service-intelligence/gcp/database/cloud-sql.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.