Microsoft EA & Licensing

SQL Server Licensing: Core vs CAL Guide 2026

SQL Server licensing is one of the most expensive and misunderstood components of the Microsoft stack. The per-core vs Server+CAL decision, virtualisation rules, and Azure Hybrid Benefit can dramatically affect your total cost.

Editorial note: This guide is part of our Microsoft EA & Licensing series. SQL Server licensing is complex and version-specific — always verify current Product Terms for your specific version and deployment scenario. Rankings are editorially independent.
$14K+
Enterprise List per 2-Core Pack
4
Minimum vCores per pCore (VM)
85%
Azure SQL Managed Instance Saving vs On-Prem
40%
Azure Hybrid Benefit Saving

SQL Server is among the most expensive software products in the Microsoft portfolio. SQL Server Enterprise per-core licensing at approximately $14,256 per 2-core pack means a single 2-socket server with 16 cores per socket requires over $228,000 in SQL Server Enterprise licences — before Software Assurance. For organisations with dozens or hundreds of SQL Server instances, this is a major cost driver in the Microsoft EA.

Understanding the two licensing models, choosing the right edition, and optimising virtualisation coverage are the three most impactful levers available to enterprise SQL Server buyers. Combined with Azure Hybrid Benefit for cloud-migrating workloads, significant cost reduction is achievable without reducing SQL Server capability.

Licensing Models: Per-Core vs Server+CAL

SQL Server offers two licensing models with fundamentally different economic profiles depending on user count and server hardware.

Per-Core Licensing

The per-core model licenses every physical (or virtual) core in the SQL Server instance and permits unlimited users and devices to access the server. This is the only model available for SQL Server Enterprise edition and the typical choice for internet-facing or high-user-count environments.

// Per-Core cost calculation
Core licences needed = MAX(4, total physical/virtual cores)
Cost = Core licences × (2-core pack price ÷ 2)

Example: SQL Server Enterprise, 2 sockets × 16 cores = 32 cores
Licences = 32 core packs (2-core each)
Cost = 16 × $14,256 = $228,096 list price

Server+CAL Licensing

The Server+CAL model charges a lower server licence fee (approximately $899 for SQL Server Standard) but requires a separate SQL Server CAL for each user or device accessing the server. This model is only available for SQL Server Standard, Web, and older Express editions.

Model Server Fee Per-User/Device User Limit Best For
Per-Core ~$3,586/2-core (Standard)
~$14,256/2-core (Enterprise)
None required Unlimited High user counts, internet-facing
Server+CAL ~$899 (Standard only) ~$209/user or device CAL Must count all users Small user count (<25), internal only
// Model decision rule

The crossover point between Server+CAL and per-core for SQL Server Standard on a 2-core server (minimum 4 cores): Per-core cost = 2 × $3,586 = $7,172. Server+CAL crossover = ($7,172 - $899) ÷ $209 = approximately 30 users. If more than ~30 users access the server, per-core is cheaper. For Enterprise edition, the crossover is much lower due to high per-core cost — Enterprise requires per-core only.

SQL Server Editions Compared

Choosing the right SQL Server edition is a significant cost decision. Enterprise edition costs approximately 4× more than Standard per core but includes features essential for mission-critical workloads.

Expert Advisory

Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.

Feature Enterprise Standard Web Developer
List price per 2-core ~$14,256 ~$3,586 Low (SP only) Free
Max memory OS max 128GB RAM 64GB RAM OS max
Max compute Unlimited 4 sockets / 24 cores 4 sockets / 16 cores Unlimited
Always On AG (readable secondaries) Yes (unlimited) Basic AG only No Yes
In-Memory OLTP Yes Limited No Yes
Columnstore indexes Yes (all) Limited No Yes
Data Compression Yes No No Yes
Advanced Analytics (R/Python) Yes No No Yes
Production use Yes Yes SP/hosting only No

Developer edition is a frequently overlooked asset — it provides full Enterprise functionality for development and testing environments at no cost. Many organisations over-pay by deploying Standard or even Enterprise in non-production environments that could use Developer edition. A compliance review should confirm all non-production SQL Server instances are correctly licensed with Developer edition where appropriate.

Virtualisation Licensing Rules

SQL Server virtualisation licensing is a major source of compliance risk and over-spend. The rules differ significantly from Windows Server virtualisation licensing.

Per-Core in VMs

When SQL Server is deployed in a virtual machine, the per-core licence covers virtual cores (vCores). The minimum is 4 vCores per VM regardless of actual vCore assignment. This means even a single-vCore SQL Server VM requires 4 vCore licences (2 × 2-core packs).

// VM core calculation
vCore licences per VM = MAX(4, assigned vCores)

Example: 5 SQL Server Standard VMs on a 16-core host
VM 1: 2 vCores → 4 vCore licences required
VM 2: 4 vCores → 4 vCore licences required
VM 3: 8 vCores → 8 vCore licences required
VM 4: 2 vCores → 4 vCore licences required
VM 5: 6 vCores → 6 vCore licences required
Total: 26 vCore licences required

Physical Host Licensing (Enterprise Only)

SQL Server Enterprise with Software Assurance provides a powerful alternative to per-VM licensing: if you license all physical cores on a Hyper-V or VMware host with SQL Server Enterprise, you gain unlimited SQL Server Enterprise VM rights on that host — similar to Windows Server Datacenter's VM model. This is economically attractive for dense SQL Server virtualisation environments.

Scenario VMs on Host Per-VM Approach Cost Host-Level Approach Cost Verdict
32-core host (2-socket × 16) 4 SQL VMs (8 vCores each) 4 × 4 = 16 packs × $14,256 = $228K 16 packs (host) × $14,256 = $228K Break-even at 4 VMs
32-core host 8 SQL VMs (4 vCores each) 8 × 2 = 16 packs × $14,256 = $228K 16 packs (host) × $14,256 = $228K Break-even at 8 VMs
32-core host 12 SQL VMs 12 × 2 = 24 packs × $14,256 = $342K 16 packs × $14,256 = $228K Host licensing saves $114K

Reviewing your SQL Server licensing position?

Our ranked advisors conduct SQL Server licence optimisation reviews and EA negotiations. Get matched.

Get Matched →

Azure SQL and Hybrid Benefit

For organisations with SQL Server workloads migrating to Azure, the Azure Hybrid Benefit is one of the most valuable Microsoft licensing rights available. SQL Server licences with active Software Assurance can be applied to Azure SQL services, dramatically reducing cloud costs.

Free Resource

Get the IT Negotiation Playbook — free

Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.

Azure SQL Deployment Options

Azure Service AHB Saving Best For
SQL on Azure VMs Up to 40% on compute Lift-and-shift workloads needing full SQL Server control
Azure SQL Managed Instance Up to 55% with AHB Near-complete SQL Server compatibility, managed PaaS
Azure SQL Database Up to 30% with AHB Cloud-native apps, lower SQL Server compatibility requirement

Azure SQL Managed Instance is increasingly attractive for organisations with complex on-premises SQL Server estates. It supports nearly all SQL Server Enterprise features in a fully managed PaaS service, reducing DBA overhead significantly while enabling AHB application. Combined with Reserved Capacity pricing (1 or 3-year commit) and AHB, SQL Managed Instance can be 55-65% cheaper than equivalent on-premises Enterprise licencing on new hardware.

SQL Server in EA Negotiations

SQL Server is typically included in Microsoft EA negotiations as a server product under the Server and Cloud Enrollment. Key negotiation considerations include:

  • Separate SQL Server from Windows Server negotiations: SQL Server pricing has different leverage dynamics. Large Azure SQL migration commitments can unlock additional SQL Server EA discounts.
  • Software Assurance is critical: SA is required for Licence Mobility, Azure Hybrid Benefit, and host-level virtualisation rights for Enterprise. It is rarely optional for large SQL Server deployments.
  • Right-size editions before renewal: A comprehensive licence right-sizing review may reveal Standard edition instances that were upgraded to Enterprise unnecessarily, or non-production servers running Enterprise that could move to Developer edition.
  • Azure migration commitment leverage: If your organisation is planning to migrate SQL Server workloads to Azure SQL, this represents significant Azure spend commitment that can be leveraged for better pricing on retained on-premises SQL Server licences through the EA.

Cost Optimisation Strategies

1. Audit all SQL Server deployments

Many organisations have significantly more SQL Server instances than their licence inventory reflects. Database servers installed for application backends, development tools with bundled SQL Express instances, and SharePoint databases running SQL Server Standard are common sources of unlicensed or under-licensed deployments. Use Microsoft's SAM engagement process proactively to identify and remediate before an audit request.

2. Rightsize editions by workload

Deploy SQL Server Enterprise only where the specific Enterprise features are genuinely required: Always On with multiple readable secondaries, In-Memory OLTP for high-throughput OLTP, or columnstore for analytical workloads. Many databases running Enterprise could operate on Standard with no performance or availability impact.

3. Migrate eligible workloads to Azure SQL

Azure SQL Managed Instance with Azure Hybrid Benefit and Reserved Capacity is cost-competitive with on-premises Enterprise for most OLTP workloads. Migrating non-critical SQL Server instances to Azure SQL Database removes licence cost entirely and moves spend to a more flexible, lower-cost operational model.

4. Use Developer edition for all non-production

Every non-production SQL Server instance (development, test, UAT, staging) should be running Developer edition. This is free, provides full Enterprise capability, and is explicitly permitted by Microsoft's Product Terms for non-production use. Remediating production licences applied to non-production environments is immediate savings with no risk.

5. Evaluate host-level licensing for dense VMs

If you have more than 8-10 SQL Server Enterprise VMs on a single physical host, licensing the host rather than individual VMs is almost always more cost-effective. For organisations planning to scale up SQL VM density on physical hardware, this is a critical planning consideration before the next EA renewal.

Frequently Asked Questions

What is the difference between SQL Server per-core and Server+CAL licensing?
SQL Server per-core licensing charges per physical or virtual core and allows unlimited user access. Server+CAL licensing charges a lower server licence fee but requires a separate Client Access Licence for each user or device. Per-core is better for internet-facing or large-user-count deployments; Server+CAL can be more cost-effective for small internal user populations — the crossover is typically around 25-30 users for Standard edition.
Which SQL Server edition do I need?
SQL Server Enterprise provides the full feature set including unlimited memory, Always On AG, advanced analytics, and partitioning — required for mission-critical databases. Standard supports up to 4 sockets or 24 cores and 128GB RAM, suitable for departmental workloads. Developer edition provides full Enterprise features for development and testing only. Most organisations use Enterprise for critical systems and Standard for smaller workloads to manage cost.
How does SQL Server licensing work in a virtual environment?
SQL Server can be licensed per virtual core in VMs, with a minimum of 4 vCores per VM. With Software Assurance's Licence Mobility, SQL Server Enterprise licences can be reassigned between servers within a server farm every 90 days. For dense environments, licensing all physical cores on a host with SQL Server Enterprise + SA covers unlimited SQL Server VMs on that host.
Can I use my SQL Server licences on Azure?
Yes — SQL Server licences with active Software Assurance can be applied to Azure virtual machines and Azure SQL services via the Azure Hybrid Benefit, reducing Azure SQL costs by up to 40-55% depending on the deployment type. This is available for SQL Server on Azure VMs, Azure SQL Managed Instance, and Azure SQL Database. See our Azure Hybrid Benefit guide for full details.

Optimise Your SQL Server Licensing Costs

SQL Server is one of the highest-cost, highest-leverage items in a Microsoft EA. Expert advisory consistently delivers 20-40% savings through edition right-sizing, virtualisation optimisation, and Azure Hybrid Benefit application.