# Underutilized Cloud SQL instance | Cloud Efficiency Hub Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/underutilized-cloud-sql-instance Cloud SQL instances are often over-provisioned or left running despite low utilization. By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Underutilized Cloud SQL Instance The short version Cloud SQL instances are often over-provisioned or left running despite low utilization. PointFive Research Cloud cost research at PointFive GCP service [GCP Cloud SQL](https://www.pointfive.co/efficiency-hub/cloud-services/gcp-cloud-sql) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0183 Type Overprovisioned Resource ## Explanation Why the waste happens and who it affects. Since billing is based on allocated vCPUs, memory, and storage - not usage - any misalignment between actual workload needs and provisioned capacity leads to unnecessary spend. Common causes include: - Initial oversizing during launch that was never revisited - Non-production environments with continuous uptime but minimal use - Databases used intermittently (e.g., for nightly reports) but kept running 24/7 Without rightsizing or scheduling strategies, these instances generate ongoing cost with limited business value. ## Billing model The pricing dimensions that drive this cost. Billed based on: - vCPU and memory provisioned, priced per hour and charged for every second the instance is running - Storage provisioned (per GB-month); IOPS and throughput are billed separately only for Hyperdisk Balanced storage, above its 3,000 IOPS and 140 MBps baseline - Backups and network egress Charges accrue regardless of utilization levels; costs reflect provisioned capacity, not actual usage. ## How to detect 5 checks to find it in your estate. - Review CPU and memory utilization trends over a representative period - Identify instances with consistently low usage relative to provisioned specs - Separate instances with no connections or query activity at all: those are idle rather than oversized, and deleting or stopping them saves more than rightsizing - Evaluate whether the environment (dev, test, QA) requires full-time availability - Examine storage and IOPS usage to identify excessive disk allocation ## How to fix 5 ways to remove the waste. - Right-size vCPU and memory allocations based on actual performance needs - Schedule automatic shutdown for non-production instances during off-hours - Use Cloud SQL's stop/start capability for intermittent workloads (stopping suspends instance charges, but storage and IP address charges continue) - Evaluate whether occasional-query workloads can move to a smaller instance, such as a shared-core machine type, or to a serverless database option - Implement monitoring to trigger reviews when utilization stays below a threshold ## Documentation Vendor references for pricing and configuration. - [Cloud SQL pricing cloud.google.com](https://cloud.google.com/sql/pricing) - [Monitor Cloud SQL instances docs.cloud.google.com](https://docs.cloud.google.com/sql/docs/mysql/monitor-instance) - [Start, stop, and restart instances docs.cloud.google.com](https://docs.cloud.google.com/sql/docs/mysql/start-stop-restart-instance) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - GCP Cloud SQL CER-0478 ### [Oversized Cloud SQL Storage After Automatic Storage Increase](https://www.pointfive.co/efficiency-hub/inefficiencies/oversized-cloud-sql-storage-after-automatic-storage-increase) Cloud SQL enables automatic storage increase by default. The service checks available storage every 30 seconds and adds capacity when free space drops below a threshold, and by default there is no upper limit. Google documents these... Databases - GCP Cloud SQL CER-0279 ### [Excessive Automated Backup Retention in Cloud SQL](https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-automated-backup-retention-in-cloud-sql) Automated Cloud SQL backups are retained longer than required by recovery objectives or governance needs. Because backups accumulate over the retention window (and can grow quickly for high-change databases), excessive retention drives... Databases - GCP Cloud SQL CER-0475 ### [Idle Cloud SQL Instance](https://www.pointfive.co/efficiency-hub/inefficiencies/idle-cloud-sql-instance) An idle Cloud SQL instance is one that is still running but no longer serves any workload: no meaningful connections, queries or data changes. Common sources are databases left behind after a migration, instances created for a test or... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.