Azure SQL Database cost: DTU vs vCore and why vCore unlocks the discounts

Quick answer

DTU bundles compute + storage + I/O into one blended unit — simple, best for small steady databases. vCore separates compute and storage, supports Hyperscale, and unlocks Azure Hybrid Benefit (use existing SQL licenses, ~55% off) and reserved capacity. For larger or license-heavy production, vCore is usually cheaper; for small databases, DTU is simpler and often cheaper.

Azure SQL Database offers the same database under two purchasing models, and the choice has real cost consequences — mostly because only one of them can access the big discounts. Understanding what each model bundles tells you which is cheaper for your workload.

DTU: the bundled model

DTU (Database Transaction Unit) blends compute, storage, and I/O into a single number across Basic, Standard, and Premium tiers. You pick a tier and a DTU level and that's the bill — no separate dials. It's simple and predictable, and for small databases the entry tiers (Basic, low Standard) are cheap. The downside: no Hybrid Benefit, no reserved capacity, and capacity planning is opaque because you can't see compute vs storage separately.

vCore: the unbundled model

vCore prices compute (number of vCores in General Purpose, Business Critical, or Hyperscale) and storage independently. It costs more to start, but it unlocks the levers that matter at scale:

Azure Hybrid Benefit — apply existing SQL Server licenses for up to ~55% off compute. See Azure Hybrid Benefit explained.
Reserved capacity — 1-3 year commitments for steady databases.
Serverless compute — auto-pauses when idle, ideal for intermittent workloads.
Hyperscale — for large databases that outgrow the other tiers.

Which is cheaper

DTU wins for small, steady databases where simplicity matters and you don't have SQL licenses to bring.
vCore wins for larger or predictable production, especially with Hybrid Benefit and reservations — the combined discounts routinely beat the equivalent DTU tier.

Other levers

Serverless (vCore) for intermittent databases — auto-pause stops compute billing when idle.
Elastic pools for many small databases that share a capacity budget instead of each provisioning its own.
Don't over-buy Business Critical — its IOPS and built-in HA cost a premium many workloads don't need.

FAQ

What's the difference between DTU and vCore pricing for Azure SQL?

DTU bundles compute, storage, and I/O into a single blended unit across Basic/Standard/Premium tiers — simple, fixed, easy to start. vCore prices compute (vCores) and storage separately, supports Hyperscale, and unlocks Azure Hybrid Benefit and reserved capacity. vCore gives more control and cost levers; DTU is simpler for small databases.

Is DTU or vCore cheaper for Azure SQL Database?

For small, steady databases, DTU (especially Basic/Standard) is often cheaper and simpler. For larger or predictable production workloads, vCore is usually cheaper overall because you can apply Azure Hybrid Benefit (use existing SQL licenses) and reserved capacity (1-3 years), discounts DTU can't access.

When should I switch from DTU to vCore?

When you outgrow the DTU tiers, need Hyperscale for large databases, want to bring SQL Server licenses via Azure Hybrid Benefit, or want reserved-capacity discounts. vCore also makes capacity planning clearer because compute and storage are separate line items rather than a blended unit.

What is Azure Hybrid Benefit for SQL?

It lets you apply existing SQL Server licenses (with Software Assurance) to vCore-based Azure SQL, removing the license portion of the compute cost — up to ~55% savings. It's only available on the vCore model, which is a major reason vCore wins for license-heavy production workloads.

How do I reduce Azure SQL Database costs?

Right-size the tier/vCores to actual usage, use serverless compute (vCore) for intermittent workloads so it auto-pauses when idle, apply Azure Hybrid Benefit and reserved capacity on steady vCore databases, use elastic pools for many small databases that share capacity, and avoid Premium/Business Critical unless you need its IOPS and HA.

How does C3X estimate Azure SQL Database cost?

C3X prices an azurerm_mssql_database from its SKU — whether DTU tier or vCore configuration — so you can compare the two models and see the effect of tier choice before deployment.

What to do next

The model and tier are set in your Terraform, so the cost is decidable before deploy. C3X prices an azurerm_mssql_database from its SKU, so you can compare a DTU tier against a vCore configuration on the same page. The quickstart runs it in minutes.