[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-03 (世界標準時間)。"],[],[],null,["# Committed use discounts\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis page describes how committed use discounts work with Cloud SQL.\n\nWhat are Cloud SQL committed use discounts?\n-------------------------------------------\n\n*Committed use discounts (CUDs)* for Cloud SQL provide deeply discounted\nprices in exchange for your commitment to continuously use database instances in\na particular region for a one- or three-year term.\n\nCloud SQL CUDs are ideal for workloads with predictable\nresource needs. You commit to a consistent amount of usage, measured in cost per\nhour of equivalent on-demand spending, for a one- or three-year term. In\nexchange, you receive a discounted rate for Google Cloud SQL on the\napplicable usage your commitment covers.\n| **Important:** This page explains the new and improved committed-use discounts (CUDs) program, which applies to any customers who purchase their first CUDs on or after **July 15, 2025** . Customers can opt in now to get the new CUD experience. For more information, see [Improvements to the spend-based CUDs\n| program](/docs/cuds-multiprice).\n\nYou can purchase CUDs from any Cloud Billing\naccount, and the discount applies to any eligible usage in projects that the\nCloud Billing account pays for. When you purchase a Cloud SQL\nCUD, you pay the same commitment fee for the entirety of the\ncommitment term, even if the price of applicable usage changes. You still\nreceive the same discount percentage on applicable usage in the event of a price\nchange. The commitment fee is billed monthly.\n| **IMPORTANT:**Any overage in usage is charged at the on-demand rate.\n\nFor more information about your bill, see [Analyze the effectiveness of your\nspend-based committed use discounts](/billing/docs/how-to/cud-analysis-spend-based).\n\nWhat types of usage are Cloud SQL CUDs used for?\n------------------------------------------------\n\nCUDs automatically apply to aggregate Cloud SQL instance\nusage in a region, giving you low, predictable costs, without the need to make\nany manual changes or updates yourself. This flexibility helps you achieve high\nutilization rates across your commitments, saving you time and money.\n\nCloud SQL CUDs apply to all Cloud SQL database\ninstance CPU and memory usage in the region in which you have committed,\n**except** shared CPU machine types (such as db-f1-micro and db-g1-small).\nCloud SQL CUDs apply to usage from all supported\ndatabases (MySQL, PostgreSQL, and SQL Server). Cloud SQL CUDs **do not\napply** to storage, backups, IP Addresses, outbound data transfer, or licensing.\n\nPricing\n-------\n\n- **25% discount**: You get this by committing to a 1-year term. For the duration of your term, you pay the Cloud SQL CUD 1-year price (consumption model ID 61F8-639B-D89C) as your committed hourly spend amount.\n- **52% discount**: You get this by committing to a 3-year term. For the duration of your term, you pay the Cloud SQL CUD 3-year price (consumption model ID 52FB-D69D-95BE) as your committed hourly spend amount.\n\nThis discount significantly reduces Cloud SQL costs. These discount percentages are the same in every region.\n\nFor a list of applicable SKUs, see [Cloud SQL CUD Eligible SKUs](/skus/sku-groups/cloud-sql-cud-eligible-skus).\n\nSee [committed use discount pricing](/sql/docs/mysql/pricing) for pricing\ndetails.\n\nPurchase Cloud SQL CUDs\n-----------------------\n\n| After your purchase a CUD, you cannot cancel your commitment. Make sure the size and duration of your commitment aligns with both your historical and your expected minimum expenditure on Cloud SQL capacity. For more information, see [Cancelling commitments](https://cloud.google.com/docs/cuds-spend-based#canceling_commitments).\n\nTo purchase or manage Cloud SQL committed use discounts for your\nCloud Billing account, follow the instructions at\n[Purchasing spend-based\ncommitments](https://cloud.google.com/docs/cuds-spend-based#purchasing).\n\nExample use case\n----------------\n\nKey points to keep in mind:\n\n- Cloud SQL CUDs apply only to vCPUs and memory.\n- Cloud SQL CUDs **do not apply** to storage, backups, IP Addresses, network egress, or licensing.\n- Cloud SQL CUDs apply to all instances in a given region.\n- Cloud SQL CUDs are measured in **dollars per hourly\n on-demand commitment**.\n- Cloud SQL CUDs can be applied to both [Cloud SQL Enterprise edition and Cloud SQL Enterprise Plus edition](/sql/docs/editions-intro). If you have an existing CUD with a Cloud SQL Enterprise edition instance and want to upgrade the instance to Cloud SQL Enterprise Plus edition, then your existing CUD can be applied to cover all or part of the cost of the newly upgraded instance.\n\n### How to calculate an hourly on-demand commitment\n\nWhen calculating the hourly rate for vCPUs and memory across all\ninstances in the region where you want to benefit from a CUD, first consider\nwhether it saves money for your situation. Any usage higher than that limit is\ncharged at the regular on-demand price.\n\nFor example:\n\n- Assume you are running 100 instances in each of two different regions. The instances are using 2 high availability (HA) vCPUs with 7.5GB HA RAM, and are located in region `us-central1` and Singapore `asia-southeast1`. You're interested in buying a 1-year CUD.\n\n| In the legacy CUDs program, your commitment amount is the on-demand price instead. For more information about the differences between the legacy and new spend-based CUDs program, see [Improvements to the spend-based CUDs program](/docs/cuds-multiprice).\n\nFrom the [pricing table](/sql/pricing#sql-cpu-mem-pricing), you can calculate the approximate hourly one-year commitment cost as follows:\n\n- `us-central1`\n\n - 100 \\* 2x HA vCPU \\* ($0.0826 per vCPU - 25% discount) per hour = \\~$12.39 per hour\n - 100 \\* 7.5GB HA RAM \\* ($0.0140 per GB - 25% discount) per hour = \\~$7.875 per hour\n - For a total of $20.27 per hour in discounted committed use hourly pricing\n- `asia-southeast1`\n\n - 100 \\* 2x HA vCPU \\* ($0.1156 per vCPU - 25% discount) per hour = \\~$17.34 per hour\n - 100 \\* 7.5GB HA RAM \\* ($0.0735 per GB - 25% discount) per hour = \\~$11.025 per hour\n - For a total of $28.37 per hour in discounted committed use hourly pricing\n\nCalculating the monthly cost (730 hours in a month):\n\n- `us-central1`\n\n - On-demand pricing = ($26.50 per hour \\* 730 hours) = $19,345 per month\n - After 25% 1-year CUD discount = \\~$14,508 per month\n - For a total savings of \\~$4,837 per month\n- `asia-southeast1`\n\n - On-demand pricing = ($35 per hour \\* 730 hours) = $25,550 per month\n - After 25% 1-year CUD discount = \\~$19,162 per month\n - For a total savings of \\~$6,388 per month\n\nOnce you make the commitment, you're charged that amount even if you decide to\nstop or scale down the actual number of vCPUs or RAM during the month.\n\nFinal recommendations\n---------------------\n\nWhen making the decision on whether to purchase CUDs, keep in\nmind the following considerations:\n\n- Regions: Purchase CUDs for regions. If you're running in multiple regions, calculate and purchase CUDs in each region separately.\n- Projects: Determine the consistent baseline vCPU/RAM usage per project. Consider that production loads usually run 100% of the time, while development or staging environments are usually run more intermittently.\n- Instances: Cloud SQL instances are usually run 24/7, so it's common to buy CUDs for 100% consumption. If you have instances that are run only for bursts or shorter durations, exclude them from your calculations, and pay on-demand rates for those instances.\n- Machine types: CUDs are not tied to any machine type, but are just the total of vCPUs and amount of memory used in the region.\n\nWhat's next\n-----------\n\n- Find CUD costs on the [pricing page](/sql/docs/mysql/pricing).\n- Learn how to purchase spend-based commitments in [Committed use discounts](/docs/cuds-spend-based)."]]
