Azure SQL cost optimization.

Azure SQL Database can be the largest line on the bill. Service tier mistakes, missed reservations, and unapplied Hybrid Benefit drive most waste.

Azure SQL Database is one of the largest hidden lines on the Azure bill. Service tier choices made early stick for years.

The cost levers are well known. Service tier, vCore count, reservation, Hybrid Benefit, and the serverless option. Most estates apply two of the five.

What follows is the framework. The service tiers, the reservation math, the Hybrid Benefit rules, and the right sizing approach that protects the line.

Service tier framework

Service tier is the largest single cost lever in Azure SQL Database.

General Purpose

Balanced compute and storage. Fits most line of business workloads. Default for new deployments unless HA needs argue otherwise.

• Compute. Provisioned or serverless on vCore base.
• Storage. Remote, premium SSD, up to four terabytes.
• HA. Standard zone or geo replication.
• Best fit. Most production line of business workloads.

Business Critical

Local SSD, low latency, in memory OLTP. Roughly three times the General Purpose cost. Only justifies on latency sensitive workloads.

Hyperscale

Storage decoupled from compute, up to one hundred terabytes, fast scale. Best fit for very large OLTP and analytics workloads.

Serverless

Pauses compute on idle. Strong fit for dev, test, and intermittent production. Can cut compute cost by sixty to ninety percent on light workloads.

Reservation strategy

Reserved capacity locks compute price for one or three years in exchange for commitment.

One year reservation

Roughly twenty four percent discount on the vCore compute line. Right for known workloads with predictable steady state load.

Three year reservation

Roughly thirty three percent discount on the vCore compute line. Best for production workloads with long term roadmaps.

Scope and exchange

Reservations can be scoped to a subscription, a management group, or shared. They can be exchanged within Azure SQL family without penalty.

Azure Hybrid Benefit stacks with reserved capacity. Combined, you can run Business Critical at the price of pay as you go General Purpose.

Azure Hybrid Benefit

Azure Hybrid Benefit reuses on prem SQL Server licenses inside Azure SQL Database and Managed Instance.

Eligibility rules

Requires active Software Assurance on the on prem SQL license. Applies to vCore Azure SQL and Managed Instance.

Conversion math

One SQL Enterprise core grants four vCores in General Purpose, or one vCore in Business Critical and Managed Instance.

Stacking with reservations

AHB stacks with reserved capacity. Combined discount on three year reservation plus AHB can hit seventy five percent vs pay as you go.

Right sizing

Right sizing happens at vCore count, at service tier, and at storage size.

vCore right sizing

Most provisioned databases run at twenty to forty percent CPU during peak. Cutting vCores by twenty five percent rarely affects SLA.

Tier down opportunities

Move dev and test from Business Critical to General Purpose. Move idle production to serverless. Both are mechanical, reversible, and immediate.

Storage tuning

Storage scales independently in Hyperscale. In General Purpose, oversized provisioned storage carries a flat monthly fee. Trim to actual.

Suggested reading

• Microsoft SQL Server audit defense. Cross vendor reading from the wider library.
• Microsoft Azure cost optimization best practices. Cross vendor reading from the wider library.

What to do next

1. Pull a complete inventory of every Azure SQL resource with tier, vCore, storage, and reservation status.
2. Tag every database by environment. Production, pre production, test, dev, and sandbox.
3. Identify Business Critical and Managed Instance resources running on dev test or low SLA workloads.
4. Confirm Software Assurance status on every on prem SQL license eligible for Azure Hybrid Benefit.
5. Model three year reservations across stable production resources.
6. Move dev and test resources to serverless or to General Purpose.
7. Set a quarterly Azure SQL review cadence to keep the line under control.

Frequently asked questions

Is Hyperscale always cheaper than Business Critical?

Not for small databases. Hyperscale carries a base storage compute envelope. Below roughly one hundred and fifty gigabytes Business Critical can be cheaper.

Can I apply Azure Hybrid Benefit on Business Critical?

Yes. One SQL Enterprise core with active SA grants one vCore in Business Critical or Managed Instance, or four vCores in General Purpose.

Does serverless support production workloads?

Yes for intermittent production. The auto pause feature suspends compute on idle. The cold start can take seconds, so latency sensitive workloads should stay provisioned.

Are reservations refundable?

Partially. Microsoft allows cancellation with a twelve percent cancellation fee. Exchanges within the Azure SQL family are free of charge.

Can I move from DTU model to vCore model?

Yes. Conversion is straightforward and usually reduces cost. The vCore model is now the default and gives access to AHB and reservations.

How often should I review Azure SQL spend?

Quarterly at minimum. Annual reviews miss the right sizing windows that open after each business change.