Azure SQL Database vs SQL Server: Features and Cost (2026)

Quick verdict

Short answer

Choose Azure SQL Database for new cloud applications that work within a single database, where you want Microsoft to handle patching, backups and high availability and you are happy to pay per database or per pool. Choose SQL Server (on your own hardware or on an Azure VM) when you need instance-level features such as SQL Server Agent, cross-database queries, CLR, linked servers or native BACKUP and RESTORE, or full control over the operating system. If you are moving an existing SQL Server estate to Azure with minimal changes, look at Azure SQL Managed Instance first.

How we know: This comparison is research-based: features, service tiers, the free offer, backup and licensing details were checked against Microsoft Learn (including the Azure SQL feature comparison page dated 30 September 2026) and the Azure pricing pages in October 2026. We have not run performance tests, and nothing here is a benchmark.

Azure SQL Database is Microsoft's relational database-as-a-service. Microsoft describes it as a fully managed SQL Server database engine "based on the latest stable Enterprise Edition of SQL Server" that always runs on the latest stable engine and a patched operating system. You create single databases or elastic pools on a logical server; there is no instance to manage and no operating system access. New engine features often arrive in Azure SQL Database before they ship in a boxed SQL Server release.

SQL Server is the same database engine as installable software. The current release is SQL Server 2025 (17.x), at Cumulative Update 9 when we checked, in Express, Standard, Enterprise and Developer editions, on Windows or supported Linux distributions. You can run it on your own servers or on an Azure virtual machine; either way you are responsible for patching, backups, high availability and upgrades.

The middle options. Azure SQL is a family of three products. Azure SQL Managed Instance is also PaaS but gives you a whole instance with, in Microsoft's words, "almost 100% feature parity with the SQL Server database engine", including SQL Server Agent, cross-database queries, CLR, Service Broker, Database Mail and native backup to Azure Blob storage; Microsoft calls it best for most migrations to the cloud. SQL Server on Azure VMs is IaaS: full SQL Server and operating system control, with 100% compatibility, but you manage it as you would on premises. See Microsoft's overview of the Azure SQL family.

Side by side

Aspect	Azure SQL Database	SQL Server
What it is	Managed database service (PaaS) in Azure	Software you install and operate: on premises, in another cloud, or on an Azure VM (IaaS)
Engine version	Latest stable engine, updated by Microsoft; compatibility controlled with database compatibility levels	The version you install (2025 is current); you choose when to patch and upgrade
Scope	Database scoped: single databases or elastic pools on a logical server	Full instance with system databases and instance-level features
SQL Server Agent	No; Microsoft points to Elastic jobs	Yes (not in Express)
Cross-database queries	No three-part names; Elastic query (preview) instead	Yes, plus linked servers
CLR, Service Broker, Database Mail	Not supported	Supported
Backups	Automatic; point-in-time restore 1 to 35 days (7 by default); long-term retention up to 10 years; no BACKUP or RESTORE statements	You plan and run them with BACKUP and RESTORE, maintenance plans or tools
High availability	Built in for every database; zone redundancy, geo-replication and failover groups available	You build it: availability groups (Enterprise; basic in Standard), failover cluster instances
Maximum database size	4 TB in General Purpose and Business Critical; 128 TB in Hyperscale	Limited by edition (50 GB in Express) and your storage
Pricing model	Pay as you go per database or pool: vCore (provisioned or serverless) or DTU; free offer available	Licence per core or Server + CAL, or subscription; Express and Developer free
Main trade-off	Less control; some SQL Server features unavailable; ongoing service cost	You own patching, backups, HA and hardware

Key differences

Features that differ or are missing in Azure SQL Database

Microsoft's feature comparison page lists what Azure SQL Database does not support compared with SQL Server and SQL Managed Instance. The items most likely to block a migration are:

SQL Server Agent: not available; Microsoft points to Elastic jobs for scheduled T-SQL.
Cross-database and three-part name queries, cross-database transactions and linked servers: not supported; Elastic query (preview) and elastic transactions cover some scenarios.
CLR, Service Broker, Database Mail and FILESTREAM: not supported.
BACKUP and RESTORE statements: not available; only automatic system backups, and you cannot restore an Azure SQL Database backup natively to SQL Server (Microsoft suggests BACPAC or BCP).
Trace flags, Windows authentication and MS DTC distributed transactions: not supported; authentication uses SQL logins or Microsoft Entra ID.
Recovery model: only full recovery, so minimal logging in bulk import is not available.
Server collation is fixed; database collation is set at creation and cannot be changed afterwards.
SSRS and SSAS are not part of the service; Microsoft points to Power BI and Azure Analysis Services.

All of these, apart from FILESTREAM, minimal logging and the BI services, are available in Azure SQL Managed Instance, which is why Microsoft positions Managed Instance for lift-and-shift migrations. Check the full list on the feature comparison page before you commit, because Microsoft updates it as features change.

Purchasing models: vCore, DTU, serverless and Hyperscale

Azure SQL Database has two purchasing models. The vCore model (which Microsoft recommends) lets you choose compute and storage independently, in three service tiers: General Purpose (budget-oriented, 1 GB to 4 TB), Business Critical (local SSD storage, three secondary replicas, one free read scale-out replica, 1 GB to 4 TB) and Hyperscale (separate compute and storage, 10 GB to 128 TB, 0 to 4 high availability replicas and named replicas for reads). Microsoft now describes Hyperscale as the recommended and default tier for new OLTP and HTAP workloads.

Within vCore you choose provisioned compute (a fixed size billed per hour) or serverless compute, which autoscales, bills per second for compute used and can auto-pause when idle so that only storage is billed. Serverless is available in General Purpose and Hyperscale. The older DTU model sells bundled compute, storage and I/O in Basic, Standard and Premium tiers, and has no serverless option. You can convert between DTU and vCore online.

On-premises SQL Server has no equivalent: you size the server, buy licences for its cores (or use Express or Developer), and the cost does not change with load.

High availability and backups

In Azure SQL Database high availability is built into every database. General Purpose separates stateless compute from storage held in Azure Blob storage; Business Critical runs a four-node cluster using technology similar to Always On availability groups; Hyperscale lets you choose the number of HA replicas. Zone redundancy, active geo-replication (up to four readable secondaries) and failover groups are configuration options rather than projects. Backups are automatic: full, differential and log backups support point-in-time restore for 1 to 35 days (7 days by default), and long-term retention keeps full backups for up to 10 years. Microsoft states that no one has direct access to the backup files.

With SQL Server you design and operate all of this yourself: backup schedules and storage, availability groups (Enterprise; Standard is limited to basic availability groups), failover cluster instances, and disaster recovery. On an Azure VM, Microsoft's SLA covers the virtual machines, not SQL Server itself, so you still configure availability groups for database-level HA. The benefit is control: you choose the recovery model, can take copy-only backups whenever you like, and can restore a backup to any compatible SQL Server.

Licensing and Azure Hybrid Benefit

Azure SQL Database prices in the vCore model (General Purpose and Business Critical) include the SQL Server licence. If you own SQL Server licences with Software Assurance or qualifying subscriptions, Azure Hybrid Benefit lets you apply them to vCore databases for a discount on the licence component. Hyperscale has no separate SQL licence fee, so Azure Hybrid Benefit is not available for new Hyperscale databases; Microsoft says existing Hyperscale single databases with provisioned compute can continue to use it until December 2026. The DTU model does not support Azure Hybrid Benefit, and reserved capacity pricing is available only in the vCore model.

SQL Server is licensed per core (Enterprise and Standard) or Server + CAL (Standard), or by subscription and pay-as-you-go through Azure Arc. On an Azure VM you can pay for the licence per minute through a SQL Server image or bring your own licence. See SQL Server Express vs Standard, Standard vs Enterprise and Express vs Developer for edition limits.

Same T-SQL, same tools

Both run the SQL Server engine, so T-SQL, data types and query behaviour are largely the same, and applications use the same drivers and connection libraries. Newer engine features such as the native json data type are available in both SQL Server 2025 and Azure SQL Database. One default differs: READ_COMMITTED_SNAPSHOT is ON by default in Azure SQL Database and OFF by default in SQL Server, so readers and writers block each other less in Azure by default.

-- Works in SQL Server, not in Azure SQL Database (no three-part names across databases)
SELECT o.id, c.name
FROM SalesDb.dbo.orders AS o
JOIN CrmDb.dbo.customers AS c ON c.id = o.customer_id;

-- Works in SQL Server, not in Azure SQL Database (no BACKUP statement)
BACKUP DATABASE SalesDb TO DISK = N'D:\backup\SalesDb.bak';

For tooling, SSMS and the MSSQL extension for VS Code connect to both. Azure Data Studio was retired on 28 February 2026 and should not be used for new work. Cross-platform clients such as DBeaver and DataGrip also connect to both.

Pricing and licensing

Azure SQL Database. Billed by Azure, per database or elastic pool. In the vCore model you pay for compute (provisioned per hour, or serverless per second of use), reserved data storage and backup storage beyond the included amount; Business Critical costs about 2.7 times General Purpose for compute because of its extra replicas, according to Microsoft Learn. Microsoft Learn states that prices start from USD 5 per month for the Basic (DTU) tier. Prices vary by region, hardware and tier, so use the Azure pricing page or calculator for your configuration. Discounts are available through reservations (vCore only) and Azure Hybrid Benefit (vCore, not Hyperscale).

Azure SQL Database free offer. Per Microsoft Learn in October 2026: up to 10 General Purpose serverless databases per Azure subscription, each with 100,000 vCore seconds of compute, 32 GB of data and 32 GB of backup storage free every month for the lifetime of the subscription. When the monthly allowance runs out you choose to auto-pause the database until next month or to continue at standard serverless rates. Free databases cannot join an elastic pool or failover group, and with auto-pause enabled are limited to 4 vCores and seven days of point-in-time restore.

SQL Server 2025. Listed on Microsoft's pricing sheet in October 2026, in US dollars, as open no-level estimated retail prices: Enterprise USD 15,123 per 2-core pack; Standard USD 3,945 per 2-core pack, or USD 989 per server plus USD 230 per CAL. Express and Developer are free. On top of licences you pay for hardware or VMs, storage, backup infrastructure and the staff time to run them.

Pricing checked on the vendors' official pages on 7 October 2026. Prices change; confirm before buying.

Where each one leads

Azure SQL Database strengths

Patching, backups, point-in-time restore and high availability are handled by Microsoft for every database
Always on the latest stable engine, so there are no version upgrades or end-of-support dates to manage
Serverless compute that autoscales and can auto-pause, plus elastic pools for many small databases
Hyperscale tier for databases up to 128 TB with fast scaling and read replicas
Free offer of up to 10 small databases per subscription for learning and prototypes

SQL Server strengths

Full instance feature set: SQL Server Agent, cross-database queries, linked servers, CLR, Service Broker, Database Mail
Complete control over configuration, patch timing, recovery model, backups and the operating system
Runs anywhere: on premises, in any cloud, on an Azure VM, or air-gapped
Free Express edition for small production use and Developer editions for dev and test
Native backups can be restored to any compatible SQL Server

Limitations

Azure SQL Database limitations

No SQL Server Agent, cross-database queries, linked servers, CLR, Service Broker or Database Mail
No BACKUP or RESTORE statements, and no native restore of its backups to SQL Server
Database scoped: instance-level settings, trace flags and Windows authentication are unavailable
Costs continue every month and depend on tier, region and usage, which needs monitoring

SQL Server limitations

You are responsible for patching, backups, monitoring, HA and disaster recovery
Full availability groups need Enterprise edition; Express has no SQL Server Agent and a 50 GB database limit
Upfront licence cost scales with cores, and each version has an end-of-support date
Scaling up usually means new hardware or a VM resize with downtime

When to choose each

Choose Azure SQL Database if

You are building a new cloud application that fits in one database or a pool of independent databases
You want backups, HA and patching handled without a DBA team
Your workload is intermittent and suits serverless auto-pause, or you run many small tenant databases
You need very large databases with fast scaling (Hyperscale)

Choose SQL Server if

Your application depends on SQL Server Agent, cross-database queries, CLR, linked servers or Service Broker
You must run on premises, in another cloud, or in an isolated network
You need control over patch timing, OS configuration or native backup files
Your workload fits in Express, or you already own SQL Server licences for the hardware

When neither is right

You are migrating an existing SQL Server instance to Azure and want PaaS without rewriting instance-level features: Azure SQL Managed Instance is Microsoft's recommended target for most migrations.
You do not need the SQL Server engine and want an open source database with no licence cost: see SQL Server vs PostgreSQL and MySQL vs SQL Server.
You need a document database rather than a relational one: see MongoDB vs SQL Server.
You are standardised on Oracle: see SQL Server vs Oracle.

Final recommendation

Bottom line

Azure SQL Database is the lower-administration choice for new, cloud-designed applications that live within a single database: Microsoft runs the engine, backups and HA, and serverless or Hyperscale cover a wide range of sizes. SQL Server remains the right choice when you need instance-level features, full control, or to run outside Azure. Before migrating an existing SQL Server database to Azure SQL Database, check every feature it uses against Microsoft's comparison list; if Agent jobs, cross-database queries or CLR show up, evaluate Azure SQL Managed Instance or SQL Server on an Azure VM instead.

Frequently asked questions

Is Azure SQL Database the same as SQL Server?

It runs the same SQL Server database engine, based on the latest stable Enterprise Edition according to Microsoft, so T-SQL and drivers are largely the same. It is a managed service scoped to individual databases, so instance-level features such as SQL Server Agent, cross-database queries, CLR and BACKUP statements are not available.

Does Azure SQL Database support SQL Server Agent?

No. Microsoft recommends Elastic jobs for scheduled T-SQL in Azure SQL Database. Azure SQL Managed Instance does support SQL Server Agent, with some differences documented by Microsoft.

Is Azure SQL Database free?

There is a free offer: up to 10 General Purpose serverless databases per subscription, each with 100,000 vCore seconds, 32 GB of data and 32 GB of backup storage per month. Beyond that it is a paid service. SQL Server Express and Developer editions are also free to run on your own hardware.

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

Both are PaaS and both are patched and backed up by Microsoft. Azure SQL Database is database scoped; Managed Instance is a full instance with near complete SQL Server compatibility, including SQL Server Agent, cross-database queries, CLR, linked servers and native backup and restore via Azure Blob storage. Managed Instance suits migrations; Azure SQL Database suits new cloud applications.

Should I choose vCore or DTU?

Microsoft recommends the vCore model. It offers higher limits, serverless compute, Hyperscale, reservations and Azure Hybrid Benefit. DTU bundles compute, storage and I/O into fixed packages, which some teams find simpler for small databases. You can switch between them online.

Can I move a database from Azure SQL Database back to SQL Server?

Not with a native backup. Microsoft documents BACPAC export or BCP as the way to move data from Azure SQL Database to SQL Server.

Sources

Checked October 2026.

How we research comparisons: our editorial method.