Azure SQL DB Pricing: Tiers and Hidden Costs Azure SQL Database is a fully managed relational database service, but there is no single price for it. Your bill comes from several independent choices: deployment model, DTU or vCore purchasing, service tier, compute mode, region, storage, backup retention, and availability.

Teams get surprised because the headline compute rate is only one line on the invoice. Storage, backups, replicas, monitoring, and networking sit outside it.

This guide gives current US examples, explains each cost component, exposes the charges people miss, and shows how to build a realistic monthly budget from Microsoft's own pricing sources.

Key Takeaways

  • DTU bundles compute and storage; vCore prices compute, storage, and extras separately.
  • General Purpose, Business Critical, and Hyperscale serve different performance and scale needs.
  • Backups, long-term retention, replicas, and always-on serverless activity can inflate the bill.
  • Right-size from measured usage, not the lowest advertised rate.

How Much Does Azure SQL Database Cost? (Pricing Overview)

All prices below are East US, USD, pay-as-you-go, as of 2026-11-18 from Microsoft's pricing page. They exclude reservations, savings plans, Azure Hybrid Benefit, credits, and taxes. Microsoft describes published prices as estimates.

Budget band Configuration Displayed charge Boundary
Entry/dev Basic, 5 DTUs $4.8971/month 2 GB included and maximum
Standard production General Purpose, 2 vCores, Gen5 $368.188/month compute Storage $0.115/GB-month extra
High-performance Business Critical, 2 vCores, Gen5 $991.976/month compute Storage $0.25/GB-month extra

These bands organize examples. They are not sizing guarantees. Each excludes excess backup storage, long-term retention, optional replicas, monitoring, networking, and support, all covered below.

DTU-Based Pricing

DTUs bundle compute, storage, and I/O into one unit. Basic, Standard, and Premium tiers scale from there.

SKU DTUs Included storage Max storage USD/month
Basic 5 2 GB 2 GB $4.8971
Standard S0 10 250 GB 250 GB $14.7187
Standard S3 100 250 GB 1,024 GB $147.1772
Premium P1 125 500 GB 1,024 GB $456.25

Microsoft positions S0 for development, testing, or infrequent access that tolerates performance variability. Resource-intensive workloads should look at S3 or higher.

Extra Standard storage runs $0.17/GB-month where supported. Billing is hourly, partial hours included, and DTU backup storage carries no additional charge.

vCore-Based Pricing

Provisioned compute bills for allocated capacity. Serverless bills per second for active compute and can auto-pause when idle.

Standard-series Gen5 Provisioned, 2 vCores/month Serverless, per vCore-second Storage/GB-month
General Purpose $368.188 $0.0001450 $0.115
Business Critical $991.976 Not supported $0.25
Hyperscale $266.684 $0.0001050 $0.25

Hyperscale replica compute is additional. Serverless bills the maximum of minimum vCores, CPU used, minimum memory divided by 3, and memory used divided by 3. A 0.5 minimum vCore with 2.1 GB minimum memory creates a 0.7-vCore billing floor.

Azure SQL serverless billing floor calculation with minimum resources

Hardware matters too. Standard-series is the reference for the prices above. DC-series is provisioned only, with no serverless or zone redundancy. Premium-series options exist for Hyperscale and must not be priced off Standard-series rates.

Deployment and Tier Context

Single databases, elastic pools, Managed Instance, and SQL Server on Azure VMs are different deployment options with different billing scopes. Prices here cover single databases and pools only.

Elastic pools share eDTUs or vCores across databases:

  • Basic, 50 eDTUs: $73.61/month
  • Standard, 100 eDTUs: $220.53/month
  • Premium, 125 eDTUs: $684.38/month

Pool charges follow the highest configured allocation, not the sum of database activity. Pools suit databases with low average use and infrequent, non-overlapping spikes.

Microsoft's own illustration of 20 databases sharing 100 eDTUs shows a 13-fold price reduction versus individual S3 databases, but that is a modeled pattern, not a customer result. Persistently busy databases make poor pool candidates, and shared capacity makes per-database cost attribution harder.

Key Factors That Affect the Cost of Azure SQL Database

Every factor below affects both monthly spend and workload fit. Tie each to a measured requirement.

Purchasing Model and Compute Mode

  • DTU: a bundled unit, simple, with less control over individual resources.
  • Provisioned vCore: predictable allocated capacity, supports Hybrid Benefit and reservations.
  • Serverless vCore: elastic billing suited to intermittent workloads.

Serverless is not automatically cheaper. Auto-pause needs zero sessions and zero user CPU for the full delay. Several conditions block pause or trigger resume:

  • Open connections, monitoring activity, and health checks
  • Geo-replication, long-term retention, and DNS aliases

Resume takes about a minute, and the first connection can fail with error 40613, so your app needs retry logic. Storage stays billable while paused.

Service Tier, Hardware, and Performance Requirements

Attribute General Purpose Business Critical Hyperscale
Storage Remote premium Local SSD Decoupled, local SSD cache
Emphasis General workloads Low I/O latency Large, independent scaling
Max size 4 TB 4 TB 128 TB
Read scale None built in One readable secondary 0-4 HA replicas, up to 30 named

Microsoft's distinctions are qualitative, so justify any upgrade with your own latency and throughput measurements. Do the same for memory-optimized or premium hardware.

Database Size, Growth, and Utilization

Data volume, transaction rate, concurrency, query complexity, I/O demand, and growth drive both compute and storage needs. Average utilization misleads. It hides peaks that cause throttling, or it justifies capacity you only need for an hour a month.

Review peak and percentile usage across a representative period. Microsoft's sizing example uses five-minute intervals and a 99.9% sample-fit objective, though that is an example, not a universal rule. Note that DTU utilization is the maximum of CPU, data I/O, and log I/O percentages, so CPU alone understates saturation.

Availability, Disaster Recovery, and Retention

Redundancy is not an automatic upgrade. Match each option to a recovery point objective, recovery time objective, or compliance need.

  • Zone redundancy: extra charge on General Purpose; none on Business Critical or Premium. Not available on DTU Basic or Standard.
  • Geo-secondaries: billed like equivalent primaries. Active geo-replication data transfer carries no extra charge.
  • Hyperscale: replicas are billable, and ZRS/GZRS backup storage is required for zone redundancy.
  • Standby replicas: license-free DR standby removes only the SQL license component, not compute or storage.

Azure SQL availability and disaster recovery options comparison

Region, Licensing, and Purchasing Commitments

Prices vary by region, so use the selector for yours. Azure Hybrid Benefit needs eligible SQL Server licenses with Software Assurance and applies to provisioned vCore only. One Enterprise core covers 4 General Purpose vCores or 1 Business Critical vCore.

Reserved capacity offers 1- or 3-year compute commitments. It excludes software, networking, and storage, and DTU is not reservable. Confirm what each discount actually covers before you bake it into a budget.

Azure SQL Database Cost Breakdown

Compute is only one line on the invoice. Map each charge below to a concrete workload requirement.

Compute (Recurring)

Provisioned and DTU compute bills hourly for allocated capacity. Serverless bills per second against the floor described earlier. Continuous operation erases serverless savings.

Data Storage (Recurring)

vCore storage is billed separately. General Purpose bills configured storage; Hyperscale bills actual allocation. DTU plans include storage up to the SKU limit. Pools bill against pool-level storage.

Backup and Long-Term Retention (Recurring or periodic)

Automated backups use weekly fulls, differentials every 12 or 24 hours, and log backups roughly every 10 minutes. PITR retention defaults to 7 days and can reach 35 (Basic: 7). LTR extends to 10 years.

For vCore single databases, the free allowance equals 100% of maximum configured data storage. Only excess is charged. Heavy writes and index rebuilds raise differential and log consumption.

Redundancy Excess PITR/GB-month LTR/GB-month
LRS or ZRS $0.10 $0.025
RA-GRS or RA-GZRS $0.20 $0.05

Azure SQL backup storage pricing by redundancy and retention type

Hyperscale includes a backup allowance equal to database size; only backup storage beyond that allowance is charged.

High Availability, Disaster Recovery, and Shared Resources (Recurring)

Zone redundancy, failover groups, extra replicas, and pool capacity all add recurring cost. Pool and instance-level charges are hard to split across databases, so decide an allocation rule up front.

Monitoring, Networking, Licensing, and Operational Overhead (Recurring or usage-based)

Item Price Scope
Azure Monitor Analytics Logs $2.30/GB ingested; first 5 GB/month free per billing account Retention and exports billed separately
Internet egress First 100 GB/month free; next 10 TB at $0.087/GB Not applied to geo-replication transfer
Private Link $0.01/hour per endpoint; $0.01/GB processed Partial hours billed as full
Support plans Developer $29, Standard $100, Professional Direct $1,000/month Per subscription, not per database

Azure SQL monitoring networking licensing and support cost comparison

Low-Cost vs High-Cost: What's the Difference?

A Basic or S0 database costs a few dollars to roughly $15 a month. It fits development, testing, and small apps, provided its storage cap and recovery limits are acceptable.

A Business Critical database runs about $992 a month for 2 vCores before storage. Justify it with measured latency, throughput, availability, or compliance needs, not a wish for headroom. The gap shows up in resilience, scale ceiling, and maintenance effort. Choose the cheaper option whenever its limits do not hurt you.

How to Estimate the Right Budget for Azure SQL Database

Budget for workload fit and total cost of ownership, not the lowest hourly compute price.

Build a Workload Baseline

Document these before touching a calculator:

  • Database size and growth rate
  • Read/write mix, plus peak and average utilization
  • Concurrency and uptime needs
  • Latency targets
  • Backup retention and recovery objectives
  • Region and compliance requirements

Create a Monthly Cost Model

Monthly cost = compute + data storage + excess backup and LTR + replicas/redundancy + monitoring + networking + licensing + taxes − verified discounts or credits

Model at least three scenarios:

  1. Intermittent dev/test: serverless or Basic, minimal retention.
  2. Continuous production: provisioned General Purpose, 7-day PITR, monitoring.
  3. High-availability: Business Critical or zone-redundant, geo-secondary, longer retention.

Three Azure SQL monthly budget scenarios from development to high availability

Validate and Revisit the Estimate

Compare your model against the Azure pricing calculator, which supports backup-retention inputs. Cross-check with Cost Management exports (daily, weekly, or monthly into Excel or Power BI) and Azure Monitor utilization.

Microsoft treats DTU-to-vCore conversion guidance as initial estimates only, so revisit the budget once real workload behavior shows up.

What Most People Miss

  • Chasing the lowest compute rate while backup growth, LTR, replicas, storage expansion, monitoring, networking, and shared-pool costs pile up.
  • Selecting serverless, Business Critical, Hyperscale, or redundancy without confirming the workload actually needs those features.

If you also run Azure VMs, block storage is a separate cost line. Lucidity provides multi-cloud visibility and autonomous optimization for cloud block storage, including AutoScaler for zero-downtime expansion and shrinking. It does not replace Microsoft's Azure SQL Database pricing or change managed-service charges.

Conclusion

Azure SQL Database pricing depends on how purchasing model, deployment, tier, compute behavior, storage, backup, availability, region, and discounts interact. No single list price captures the full bill.

Build a workload-based estimate from official pricing sources that covers both visible compute and hidden operational costs:

  • Right-size from measured usage
  • Review billing data regularly
  • Pay for premium options only when they deliver a clear performance, resilience, or recovery benefit

Frequently Asked Questions

Is Azure SQL DB free?

Partly. Each subscription gets up to 10 General Purpose databases with 100,000 vCore-seconds, 32 GB data, and 32 GB backup monthly. This differs from the $200 30-day free account credit. Verify eligibility and limits on Microsoft's site.

What are the different tiers of Azure SQL Database service?

DTU offers Basic, Standard, and Premium. vCore offers General Purpose, Business Critical, and Hyperscale. Choose by workload requirements, not tier names.

What are the differences between Azure SQL Database Hyperscale and General Purpose?

Hyperscale supports up to 128 TB versus 4 TB, with decoupled storage and up to 30 named replicas. General Purpose uses remote premium storage with no built-in read scale. Both price compute and storage separately.

What is the difference between an Azure SQL Database and an Azure SQL Managed Instance?

SQL Database deploys as a single database or elastic pool. Managed Instance is an instance-level managed SQL Server environment, suited to migrations needing broader compatibility. Billing scopes differ, so don't reuse database prices.

What types of SQL databases are available in Azure?

Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure Virtual Machines. Each has its own operational and pricing model.

What is the backup policy for Azure SQL Database?

Automated PITR backups default to 7 days, configurable to 35 (Basic: 7). Optional LTR runs up to 10 years. Only backup storage beyond the allowance is charged, so check current terms for your model and tier.