# Missing Reservation or Savings Plan Coverage for Steady-State Azure SQL vCore Compute Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/missing-reservation-or-savings-plan-coverage-for-steady-state-azure-sql-vcore-compute Provisioned vCore databases in Azure SQL Database and instances in Azure SQL Managed Instance are billed hourly for compute at pay-as-you-go rates... By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) The short version Provisioned vCore databases in Azure SQL Database and instances in Azure SQL Managed Instance are billed hourly for compute at pay-as-you-go rates unless a commitment discount applies. PointFive Research Cloud cost research at PointFive Azure service [Azure SQL](https://www.pointfive.co/efficiency-hub/cloud-services/azure-sql) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0434 Type Suboptimal Pricing Model ## Explanation Why the waste happens and who it affects. Production databases typically run around the clock at a stable size for years, which is exactly the usage pattern Azure Reservations and the Azure savings plan for databases are designed to discount. A reservation needs no assignment: once purchased, matching compute in its scope is discounted automatically, with no change or failover on the databases themselves. Coverage is often missing because database teams size and operate the servers while a separate finance or cloud team owns commitment purchases, so steady SQL compute keeps running at list price. Azure Advisor surfaces this with the High-impact recommendation 'Consider SQL PaaS DB reserved instance to save over the pay-as-you-go costs'. The opportunity is limited to compute: reservations do not apply to DTU-based databases or to SQL Database serverless, and they do not cover software, storage or networking charges. ## Billing model The pricing dimensions that drive this cost. Azure SQL vCore compute can be billed at pay-as-you-go rates or discounted through one of two commitments. Pay-as-you-go vCore compute Billed hourly for provisioned compute based on service tier, hardware and vCore count SQL reservation A 1- or 3-year commitment for a region, deployment type, performance tier and vCore quantity, applied hourly to primary and billable secondary replica compute vCore ZR reservation A separate reservation type needed to discount the zone-redundancy add-on for SQL Database General Purpose and SQL Managed Instance General Purpose and Business Critical Use-it-or-lose-it hours Reserved hours with no matching compute in scope are lost and cannot be carried forward Savings plan for databases A 1- or 3-year hourly spend commitment that applies across eligible database services, including Azure SQL Database, SQL Managed Instance, Hyperscale and serverless ## How to detect 4 checks to find it in your estate. - Review Azure Advisor Cost recommendations for 'Consider SQL PaaS DB reserved instance to save over the pay-as-you-go costs' and for savings plan purchase recommendations - In Cost Management, group Azure SQL Database and SQL Managed Instance compute cost by pricing model to find vCore compute that is charged OnDemand rather than Reservation or SavingsPlan - Identify provisioned vCore databases and managed instances that have run continuously at a stable vCore count for the lookback period, grouped by region, deployment type, service tier and hardware - For zone-redundant General Purpose databases and managed instances, check whether a vCore ZR reservation covers the zone-redundancy add-on ## How to fix 6 ways to remove the waste. - Buy SQL Database or SQL Managed Instance reservations sized to the stable baseline vCore count per region, service tier and hardware, keeping bursty or short-lived capacity on pay-as-you-go - Use shared or management group scope so the discount follows matching compute across subscriptions, and rely on vCore size flexibility to scale within a tier and region without losing the benefit - Add vCore ZR reservations where zone redundancy is enabled, since a standard vCore reservation does not discount the zone-redundancy add-on - Where the SQL estate is changing (tier moves, serverless adoption, region changes), consider the savings plan for databases instead, which trades a smaller discount for flexibility across services and regions - Note that reservations bought from February 1, 2027 for savings-plan-eligible services such as SQL Database cannot be exchanged, so size commitments conservatively - Apply Azure Hybrid Benefit separately to cover SQL Server license charges, which reservations do not discount ## Documentation Vendor references for pricing and configuration. - [Save on compute costs with Azure Reservations - Azure SQL Database & SQL Managed Instance learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-sql/database/reservations-discount-overview) - [Understand reservations discount for Azure SQL Database learn.microsoft.com](https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/understand-reservation-charges) - [What are savings plans? learn.microsoft.com](https://learn.microsoft.com/en-us/azure/cost-management-billing/savings-plan/savings-plan-overview) - [Cost recommendations - Azure Advisor learn.microsoft.com](https://learn.microsoft.com/en-us/azure/advisor/advisor-reference-cost-recommendations) - [Self-service exchanges and refunds for Azure Reservations learn.microsoft.com](https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations) - [Pricing - Azure SQL Database Single Database azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/azure-sql-database/single/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure SQL CER-0239 ### [Azure Hybrid Benefit Not Enabled on SQL Databases](https://www.pointfive.co/efficiency-hub/inefficiencies/azure-hybrid-benefit-not-enabled-on-sql-databases-41927) Azure Hybrid Benefit allows organizations to apply existing SQL Server licenses with Software Assurance or qualifying subscriptions to Azure SQL Databases. When this configuration is missed or not enforced, workloads continue to incur... Databases - Azure SQL CER-0194 ### [Overbilling Due to Frequent Tier Switches in DTU Model](https://www.pointfive.co/efficiency-hub/inefficiencies/overbilling-due-to-tier-switches-and-allocation-overlaps-in-dtu-model) Workloads that frequently scale up and down within the same day-whether manually, via automation, or platform-managed-can encounter hidden cost amplification under the DTU model. Azure SQL Database bills each hour at the highest service... Databases - Azure SQL CER-0264 ### [Suboptimal Use of Serverless Compute for Azure SQL Database](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-use-of-serverless-compute-for-azure-sql-database-4fe48) Serverless is attractive for variable or idle workloads, but it can become more expensive than Provisioned compute when database activity is high for long portions of the day. As active time increases, per-second compute accumulation... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.