SQL Server 2022 Licensing Models and Pricing
SQL Server 2022 is available under two primary licensing models — Per-Core and Server+CAL — plus subscription and pay-as-you-go alternatives. The Enterprise Edition is available only under Per-Core licensing. Standard Edition supports both Per-Core and Server+CAL. Selecting the wrong model is the most common source of SQL Server overspend, with the cost differential between an optimal and suboptimal choice frequently exceeding $100K–$500K+ across a multi-server deployment.
| Licensing Model | List Price (USD) | Best For | Key Requirement | Key Risk |
|---|---|---|---|---|
| Enterprise — Per-Core | ~$15,123 per 2-core pack | Mission-critical workloads; unlimited virtualisation with SA; Enterprise-only features | Minimum 4 cores per physical processor (minimum 2 packs per processor) | 4× cost of Standard; over-deployed where Standard would suffice |
| Standard — Per-Core | ~$3,945 per 2-core pack | Medium-to-large user bases; virtualised environments; internet-facing applications | Minimum 4 cores per physical processor | Still significant cost at scale; 24-core cap per instance |
| Standard — Server+CAL | ~$989/server + ~$230/CAL | Small internal applications with limited, identifiable user population (<100 users) | Every accessing user or device needs a CAL (including indirect access) | CAL count grows with users; not viable for external-facing or large deployments |
| Subscription (EA/CSP) | ~$5,434/year per 2-core (Ent); ~$1,418/year (Std) | Annual payment model; includes SA benefits; cloud integration | Enterprise Agreement or Cloud Solution Provider programme | Higher total cost over 3+ years vs perpetual; locked into annual payments |
| Pay-As-You-Go (Azure Arc) | ~$274/core/month (Ent); ~$73/core/month (Std) | Short-term projects; seasonal/elastic workloads; uncertain demand | Azure Arc agent installed; Azure subscription required | 3–5× more expensive than perpetual over 3+ years for steady workloads |
| Developer / Express | Free | Non-production development (Developer); very small databases under 10 GB (Express) | Developer: no production use permitted. Express: size and feature limitations | Using Developer Edition in production = full audit exposure for Enterprise pricing |
Microsoft requires a minimum of 4 core licences per physical processor, regardless of the actual core count. A 2-socket server with 2-core processors still requires 8 core licences (4 per socket). At Enterprise pricing, this minimum costs $60,492 even for a small server. More critically, modern servers with 16–32 cores per socket drive licensing costs to $121K–$242K per server for Enterprise Edition. This makes hardware selection a licensing decision: choosing a 2-socket/16-core server over a 2-socket/32-core server saves $121,000 in SQL Server Enterprise licensing alone. Always evaluate SQL Server licensing cost alongside hardware procurement decisions.
Enterprise vs Standard Edition — Feature and Cost Comparison
| Capability | Enterprise Edition | Standard Edition |
|---|---|---|
| List price (2-core pack) | $15,123 (~4× Standard) | $3,945 |
| Maximum compute | OS maximum (unlimited cores) | Lesser of 4 sockets or 24 cores |
| Maximum memory | OS maximum (unlimited) | 128 GB per instance |
| Virtualisation rights (with SA) | Unlimited VMs on fully licensed host | Maximum 2 VMs (licensing the virtual cores of each) |
| Always On Availability Groups | Full (unlimited replicas, read-scale secondaries) | Basic only (2-node, no read secondaries) |
| Transparent Data Encryption (TDE) | Included | Not available |
| Table partitioning | Included | Not available |
| Data compression | Full (row + page + columnstore) | Limited |
| In-Memory OLTP | Included (unlimited) | Limited (32 GB cap) |
| Failover rights (with SA) | 1 passive secondary (no licence required) | 1 passive secondary (no licence required) |
The Enterprise Over-Deployment Problem
Across hundreds of Microsoft licensing assessments, we consistently find that 30–50% of SQL Server Enterprise Edition deployments do not use any Enterprise-exclusive feature. These databases could run on Standard Edition at 75% lower cost. On a 2-socket, 16-core server, the difference is $121,000 (Enterprise) vs $31,560 (Standard) — a savings of $89,440 per server. For an enterprise with 10 such servers, that represents $894,400 in recoverable licensing cost. The most common reason for Enterprise over-deployment: the database was originally installed as Enterprise Edition "just in case," and no one ever validated whether Enterprise features were actually required. Conduct a feature-usage audit on every Enterprise Edition instance — the savings opportunity is almost always significant.
Server+CAL Breakeven Analysis — When Each Model Wins
| Scenario | Server+CAL Cost | Per-Core Cost | Cheaper Model | Savings |
|---|---|---|---|---|
| 25 users, 8-core server (Standard) | $989 + (25 × $230) = $6,739 | 4 × $3,945 = $15,780 | Server+CAL (57% cheaper) | $9,041 |
| 50 users, 8-core server | $989 + (50 × $230) = $12,489 | $15,780 | Server+CAL (21% cheaper) | $3,291 |
| 75 users, 8-core server | $989 + (75 × $230) = $18,239 | $15,780 | Per-Core (13% cheaper) | $2,459 |
| 100 users, 16-core server | $989 + (100 × $230) = $23,989 | 8 × $3,945 = $31,560 | Server+CAL (24% cheaper) | $7,571 |
| 200 users, 16-core server | $989 + (200 × $230) = $46,989 | $31,560 | Per-Core (33% cheaper) | $15,429 |
| Internet-facing (unlimited users) | Not viable — cannot CAL unknown users | $15,780–$31,560+ depending on cores | Per-Core (only option) | N/A |
Virtualisation and Cloud Licensing Rules
SQL Server 2022 significantly tightened virtualisation licensing requirements. The most critical change: Software Assurance (SA) is now effectively required for any VM-level licensing. Without SA, you must licence all physical cores on the host server — regardless of how many cores are allocated to the SQL Server VM. This change alone can multiply licensing costs by 2–10× in virtualised environments.
| Environment | Licensing Rule | SA Requirement | Cost Impact |
|---|---|---|---|
| Physical server | Licence all physical cores (min 4 per processor) | Not required for basic licensing | Straightforward; cost scales with core count |
| VM — with SA (vCore licensing) | Licence only the virtual cores assigned to the SQL Server VM (min 4 vCores) | SA required | Efficient; licence only what the VM uses |
| VM — without SA | Must licence ALL physical cores on the host server | Not applicable (no SA = full host licensing) | 2–10× more expensive; a 32-core host = $63K+ Standard or $242K+ Enterprise |
| Enterprise + SA (unlimited virtualisation) | Licence all physical cores on the host → run unlimited SQL Server VMs on that host | SA required | Cost-effective for high VM density (5+ SQL VMs per host) |
| Azure (Azure Hybrid Benefit) | BYOL existing SQL Server licences with SA to Azure VMs or Azure SQL; reduces Azure compute cost | SA required for AHB | Up to 55% savings on Azure SQL compute vs pay-as-you-go |
| AWS / GCP (Licence Mobility) | Licence Mobility through SA allows deploying SQL Server licences on authorised cloud provider shared infrastructure | SA required | Enables BYOL to non-Microsoft clouds; form must be submitted to Microsoft |
| Azure Arc pay-as-you-go | On-premises SQL billed per-core/per-month through Azure subscription; no upfront licence purchase | Not required (subscription model) | ~$274/core/month (Ent); breakeven vs perpetual at 3–4 years |
Failover and Disaster Recovery Licensing Rights
| Failover Scenario | Additional Licence Required? | Condition | Key Consideration |
|---|---|---|---|
| Passive secondary (cold standby) | No — free with SA | Server must be truly passive (no queries, reporting, or maintenance workloads) | 1 free passive secondary per licensed primary; SQL Server must have active SA |
| Active secondary (read workload) | Yes — full licensing required | Any read or write workload on the secondary requires its own licences | Always On readable secondaries (Enterprise only) require full per-core licensing on the secondary |
| Always On Basic (Standard) | No — 1 passive replica free with SA | Standard Edition supports 2-node Basic AG with 1 passive replica; no readable secondaries | If secondary is used for any read workload, it must be fully licensed |
| Log shipping / database mirroring | No — passive secondary free with SA | Secondary must remain passive (no user connections for queries or reporting) | Secondary used for reporting, backups, or maintenance = fully licensable |
| Failover cluster instance (FCI) | No — passive node free with SA | Passive FCI node runs no SQL workload; only 1 passive node per licensed active node | If additional nodes are active simultaneously, each requires full licensing |
Common Audit Findings and Compliance Risks
| Audit Finding | How It Occurs | Typical Cost Impact | Prevention Strategy |
|---|---|---|---|
| Enterprise deployed where Standard suffices | Enterprise Edition installed by default or "just in case"; no Enterprise-exclusive features actually used | $50K–$120K over-licensing per server | Audit feature usage (sys.dm_db_persisted_sku_features); downgrade to Standard where possible |
| VM licensing without SA | SQL Server deployed on VMs without Software Assurance; Microsoft requires licensing all physical host cores | $100K–$500K+ per host (entire physical server licensed) | Ensure SA coverage for all virtualised SQL Server deployments; or isolate SQL VMs on dedicated hosts |
| Under-licensed core count | Physical cores added during hardware upgrade or VM core allocation increased without corresponding licence addition | $15K–$60K per 2-core pack gap | Implement change management process requiring licence review for any hardware or VM configuration change |
| Missing CALs (Server+CAL model) | New users or devices accessing SQL Server without corresponding CAL purchase; indirect access through middleware not counted | $230 per missing CAL × user count | Audit all direct and indirect SQL Server access paths; consider switching to Per-Core if CAL count is growing |
| Active failover server not licensed | Secondary SQL Server used for read workloads, reporting, or maintenance — not just passive standby | $30K–$240K (full licensing of secondary server) | Enforce strict passivity on failover servers; if read workload is required, budget for full secondary licensing |
| Developer Edition in production | SQL Server Developer Edition (free) used for production workloads; Developer licence prohibits production use | $60K–$240K+ (back-licensing at Enterprise per-core rates) | Audit all SQL Server instances for edition; replace Developer Edition with properly licensed Standard or Enterprise |
Cost Optimisation Strategies
| Strategy | How It Works | Typical Savings | Implementation Approach |
|---|---|---|---|
| Edition right-sizing | Identify Enterprise Edition instances not using Enterprise-exclusive features; migrate to Standard Edition | $50K–$120K per server (75% per-server reduction) | Query sys.dm_db_persisted_sku_features on each instance; if no Enterprise features returned, candidate for Standard |
| Core count optimisation | Right-size server and VM core allocations to match actual SQL Server workload CPU requirements | 20–40% per-server savings | Analyse CPU utilisation over 30+ days; reduce VM vCPU allocation; select smaller physical hardware for new deployments |
| Server+CAL conversion | Switch from Per-Core to Server+CAL for Standard Edition instances with fewer than ~65 users (8-core server breakeven) | $5K–$15K per eligible server | Inventory user counts for each Standard instance; convert when CAL count is below breakeven |
| Enterprise consolidation (unlimited VMs) | Consolidate multiple SQL Server VMs onto fewer physical hosts fully licensed with Enterprise + SA (unlimited virtualisation) | 30–60% vs licensing each VM individually | Dedicate hosts for SQL Server VMs; licence all physical cores with Enterprise + SA; run maximum VM density |
| Azure Hybrid Benefit | Apply existing SQL Server licences (with SA) to Azure VMs or Azure SQL; reduces cloud compute cost | Up to 55% on Azure SQL compute | Apply AHB in Azure portal for each SQL VM or managed instance; requires active SA on corresponding licences |
| Developer Edition for non-production | Replace licensed Standard/Enterprise instances in dev, test, QA with free Developer Edition | $15K–$120K per non-production server | Developer Edition is functionally identical to Enterprise; reclaim production licences for redeployment |
| EA negotiation and discount optimisation | Negotiate SQL Server pricing within Microsoft Enterprise Agreement; benchmark against typical discount levels | 15–35% off list pricing | Benchmark against industry discount data; leverage competitive alternatives (PostgreSQL, Oracle); time negotiation to Microsoft fiscal year-end (June) |
SQL Server 2022 Licensing Governance Checklist
Ongoing Compliance Disciplines
Complete SQL Server inventory
Maintain an up-to-date inventory of every SQL Server instance across all environments: edition (Enterprise, Standard, Developer, Express), version (2022, 2019, etc.), licensing model (Per-Core, Server+CAL, subscription), core count (physical and virtual), SA status, and deployment environment (physical, VM, cloud). This inventory is the foundation for compliance and optimisation.
Edition feature-usage audit
Run sys.dm_db_persisted_sku_features on every Enterprise Edition instance. If no Enterprise-exclusive features are returned, the database is a candidate for Standard Edition migration. Conduct this audit annually and after any major application change. Target: identify 30–50% of Enterprise instances for potential downgrade.
Virtualisation compliance verification
For every SQL Server VM, verify that the underlying licences have active Software Assurance. Confirm that core allocations match licence quantities. For Enterprise + SA hosts, verify that all physical cores are licensed and document VM density. Flag any SQL Server VM running without SA — this is the highest-risk compliance gap.
Failover server passivity enforcement
Verify that all passive failover servers are truly passive — no user connections, no reporting queries, no maintenance workloads. Any active use of a failover server requires full licensing. Implement network access controls to prevent accidental connection to passive secondaries.
Hardware change licence reconciliation
Whenever physical servers are upgraded, VMs are resized, or new SQL Server instances are deployed, reconcile the licensing impact before changes are implemented. A core count increase without corresponding licence addition creates immediate compliance exposure.
EA true-up preparation
Before each annual Enterprise Agreement true-up, reconcile SQL Server deployments against licence entitlements. Identify any new deployments or core count changes since the last true-up. Plan licence additions strategically to benefit from volume pricing tiers. Prepare negotiation positions for any pricing discussions.