Azure SQL Tiers: DTU vs vCore Pricing Explained Azure SQL Database sells capacity two ways, and the billing units don't line up. DTU bundles CPU, memory, and I/O into one preset number. vCore exposes compute as virtual cores and prices storage and extras separately.

Pick wrong and you overprovision, throttle under load, or miss discounts. Most teams compare headline rates and stop there, which is where the surprises start.

This guide compares the two models, shows where each fits, and gives a practical selection process using Microsoft's East US list prices (USD, pay-as-you-go, observed November 2026).

Key Takeaways

  • DTU bundles compute, memory, and I/O; vCore lets you size compute on its own.
  • Purchasing models are not service tiers: DTU and vCore describe how you buy capacity.
  • Predictable, smaller workloads fit DTU; control, serverless, and discounts favor vCore.
  • The lowest headline rate often isn't the lowest total cost.
  • Validate with real metrics, the pricing calculator, and a load test.

DTU vs vCore: Quick Comparison

Microsoft's purchasing models guide separates the two clearly. Basic, Standard, and Premium are DTU service tiers. General Purpose, Business Critical, and Hyperscale are vCore service tiers.

Factor DTU vCore
Billing unit Bundled CPU, memory, reads, writes Virtual cores plus a service tier
Service tiers Basic, Standard, Premium General Purpose, Business Critical, Hyperscale
Compute Provisioned only Provisioned or serverless
Hardware choice Not selectable Selectable
Storage Fixed allowance per size (S3: 250 GB included) Priced separately
Reserved capacity Not eligible Provisioned vCore, 1- or 3-year
Azure Hybrid Benefit Not eligible Provisioned vCore only
Managed Instance Not offered vCore only

Reference list prices

On the official Azure pricing page (East US, single database, no discounts):

  • Standard S3 (100 DTUs): $147.1772/month, with 250 GB included
  • General Purpose provisioned, 2 vCores, Gen5: $0.505/hour, storage billed separately
  • General Purpose serverless, Gen5: $0.0001450 per vCore-second

These aren't performance-matched. S3 and a 2-vCore database are different sizes, so don't read one as the equivalent of the other. Prices are estimates, and region, hardware, and agreement terms change them.

Azure SQL Database DTU and vCore pricing comparison infographic

Costs beyond compute

  • PITR backup is included in DTU pricing; vCore includes an allowance, then charges per GB/month for the excess.
  • Long-term retention (up to 10 years) is billed separately in both models.
  • Serverless savings plans are a different mechanism from reservations and Hybrid Benefit.

What Are DTU and vCore in Azure SQL Database?

What is DTU?

A Database Transaction Unit blends CPU, memory, reads, and writes into one measure. Buying is easy: pick a size, pay a fixed monthly amount. Optimizing is harder, because you can't see or tune the individual resources.

Current single-database limits:

Tier DTUs Max storage
Basic 5 2 GB
Standard 10-3,000 250-1,024 GB
Premium 125-4,000 1,024-4,096 GB

When DTU fits

  • Small production databases
  • Dev and test environments
  • Steady applications where a flat bill matters more than tuning

DTU struggles when workloads are CPU-bound, memory-sensitive, or highly variable. You can't pick hardware, and hitting any one resource limit throttles throughput, causing slow queries or timeouts. Basic and Standard also lack zone redundancy.

What is vCore?

A vCore is a logical CPU. You choose compute, hardware, and service tier separately from storage. Provisioned compute bills for allocated capacity. Serverless scales within a range you set, bills per second, and can auto-pause.

vCore service tiers

  • General Purpose: compute is separate from data held in remote storage, with 5-10 ms latency and up to 4 TB.
  • Business Critical: local SSD on a four-node cluster, around 1-2 ms latency, for latency-sensitive production.
  • Hyperscale: up to 128 TB per database, independent compute scaling, and 0-4 HA secondary replicas.

vCore fits teams with existing SQL Server licenses, since Azure Hybrid Benefit applies to provisioned compute.

Serverless: when it helps

Serverless suits intermittent dev, staging, or internal workloads. General Purpose auto-pause delay runs from 15 to 10,080 minutes (default 60). Paused databases bill storage only.

Resume takes about a minute, and the first connection returns error 40613, so apps need retry logic. Geo-replication, failover groups, long-term retention (LTR), and active sessions block auto-pause. If a database stays busy, provisioned compute is usually the better bet.

Azure SQL serverless auto-pause and resume behavior flowchart

DTU vs vCore: What Is Better?

Neither is universally cheaper. The answer depends on workload behavior, required controls, and total cost.

Choose DTU when:

  • Usage is predictable
  • You want one bundled bill
  • Resource-level tuning isn't needed
  • DTU limits and availability meet your requirements

Choose vCore when:

  • You need transparent sizing or separate compute and storage decisions
  • Serverless, Business Critical, or Hyperscale are on the table
  • Hybrid Benefit or reservations would cut cost
  • You want a clear path from on-premises SQL Server

Let metrics decide

Collect a representative period of data. DTU percentage is the highest of CPU, data I/O, and log I/O, so one bottleneck sets the value.

From sys.dm_db_resource_stats, review:

  • avg_cpu_percent
  • avg_data_io_percent
  • avg_log_write_percent
  • avg_memory_usage_percent

Also capture peak utilization, storage and backup growth, idle periods, and availability needs.

Model total cost

  1. Build equivalent configurations in the Azure pricing calculator.
  2. Include compute, storage, backup, redundancy, retention, licensing, reservations, and pool charges.
  3. Run a controlled performance test on both.
  4. Compare monthly totals, not hourly rates.

Four-step Azure SQL total cost evaluation process diagram

Migrating from DTU to vCore

Microsoft's starting points are about 1 vCore per 100 Basic/Standard DTUs, or 1 per 125 Premium DTUs. Basic and Standard map to General Purpose; Premium maps to Business Critical. These ignore hardware differences, so refine using IOPS, log throughput, and memory per core.

The process resembles a DTU scale operation, with brief downtime at the end. Plan rollback carefully: returning to DTU is supported, but Hyperscale reversal only works within 45 days and goes through General Purpose first.

Monitor closely after cutover.

Real-World Examples

Provisioned to serverless: Inlitix

Analytics firm Inlitix moved from fixed-price provisioned compute to serverless. According to Microsoft's customer story, dev/QA costs fell "10 times," and production savings can reach 15 times depending on usage.

Those figures are customer-reported and workload-specific. They are not a DTU-vs-vCore comparison.

Modeled scenario: intermittent staging database

Take a staging database used a few hours each weekday. A serverless setup with 0.5 minimum vCores and a 60-minute pause delay bills compute only while active and during the idle delay. Storage still bills continuously.

Watch three things:

  • The pause delay itself is billed. In Microsoft's example, a 6-hour delay billed 8 hours for 2 hours of activity.
  • Wake-up takes about a minute, and the first connection often fails.
  • Steady overnight jobs or open connections prevent pausing, which erases the savings.

Microsoft publishes no universal break-even utilization, so model your own usage hours.

Look beyond the database

SQL tier and backup costs are only part of the bill. If your architecture also runs Azure VM managed disks or other block storage, those often hide waste.

Lucidity's free Assessment scans a cloud environment in about 5 minutes, with no agents, and flags overprovisioned and idle disks. It sits alongside, not in place of, your Azure SQL tier and backup management.

Conclusion

Choose DTU for simplicity and predictable bundled capacity when its limits fit. Choose vCore for granular control, serverless, advanced tiers, and potential Hybrid Benefit or reservation savings.

Either way, decide with current regional pricing, workload telemetry, total-cost modeling, and a performance test, not a list-price comparison.

Frequently Asked Questions

Does Azure SQL Database have a free tier?

Yes. Each database gets 100,000 vCore seconds, 32 GB data, and 32 GB backup monthly, for up to 10 databases per subscription. Past the limit, you pause until next month or pay standard rates. There's no SLA.

What are the different tiers of Azure SQL Database?

DTU offers Basic, Standard, and Premium. vCore offers General Purpose, Business Critical, and Hyperscale. Availability varies by deployment model.

What are the different types of Azure SQL databases?

The Azure SQL family includes Azure SQL Database (single database and elastic pool), SQL Managed Instance, and SQL Server on Azure Virtual Machines. Only the first is compared here.

Is Azure SQL Database a PaaS or a SaaS?

Microsoft classifies it as a fully managed platform-as-a-service database engine. Microsoft handles patching, upgrades, backups, and monitoring. You manage configuration and workloads.

Which is cheaper, DTU or vCore?

It depends on size, utilization, storage, backup, region, discounts, and licensing. Compare equivalent configurations rather than entry-level prices.

Can you migrate an Azure SQL Database from DTU to vCore?

Yes. Assess compatibility and sizing, plan the cutover, validate performance, and follow Microsoft's DTU-to-vCore migration documentation. Returning to DTU is also supported, with Hyperscale restrictions.