Missing Reservation or Savings Plan Coverage for Steady-State Azure SQL vCore Compute

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.

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

• 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

• 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

• Save on compute costs with Azure Reservations - Azure SQL Database & SQL Managed Instancelearn.microsoft.com
• Understand reservations discount for Azure SQL Databaselearn.microsoft.com
• What are savings plans?learn.microsoft.com
• Cost recommendations - Azure Advisorlearn.microsoft.com
• Self-service exchanges and refunds for Azure Reservationslearn.microsoft.com
• Pricing - Azure SQL Database Single Databaseazure.microsoft.com