The Two Licensing Models: An Overview
Microsoft SQL Server can be licensed under two distinct models: Per Core and Server + Client Access License (CAL). Understanding which model applies to your workload is the foundation of SQL Server cost management.
The choice between these models has profound financial implications. A four-socket server with per-core licensing could cost £40,000+, while the same hardware under Server+CAL might cost £10,000–£15,000. Conversely, a deployment with hundreds of users accessing a single server may be far cheaper on per-core licensing than on CAL. The wrong choice can compound over three years of EA contract periods, turning into hundreds of thousands of pounds in avoidable costs.
Both models are legitimate and officially supported. Neither is inherently cheaper—it depends entirely on your architecture, user count, and virtualisation strategy.
Free Guide
Microsoft EA Negotiation Tactics
How Fortune 500 buyers slash Microsoft EA costs — true-up traps, ELP rules, and renewal leverage.
Per-Core Licensing Model: Technical Deep Dive
How Per-Core Licensing Works
Under the per-core model, you license SQL Server based on the physical processor cores in each server. Microsoft's current minimum is 4 cores per processor, sold in 2-core packs. This means:
- A dual-socket server with 8 cores per socket = 16 cores total = requires 8 two-core packs of Enterprise SQL Server licenses
- All physical cores in the processor socket must be licensed, even if you only use some of them
- You cannot "turn off" unused cores or gain credit for licensing only half a socket
- Hyper-threading (logical cores) is ignored—only physical cores count
The per-core model includes unlimited user and device access. There are no CALs. Once you own the per-core licenses, any number of users or devices can connect to that instance.
Per-Core Pricing Context
As of 2026, Microsoft's list pricing for per-core SQL Server Enterprise is approximately £3,586 per 2-core pack. On a dual-socket, dual-core-per-socket server (4 cores total), you'd need 2 packs = ~£7,172 per server. However, EA agreements typically negotiate 15–40% discounts from list, making actual costs £4,300–£6,100 per server.
For a larger server—say a 4-socket system with 12 cores per socket (48 cores)—you need 24 two-core packs, pushing the cost to ~£86,064 at list (or £51,600–£73,000 with EA discount). This is why infrastructure teams often cap server sizing when moving to per-core: over-provisioning cores becomes prohibitively expensive.
Stay Ahead of Vendors
Get Negotiation Intel in Your Inbox
Monthly briefings on vendor pricing changes, audit trends, and contract tactics. Unsubscribe any time.
No spam. No vendor affiliations. Buyer-side only.
The Per-Core Advantage: When It Pays
Per-core licensing excels when:
- High user/device concurrency: If hundreds or thousands of users need access, per-core is almost always cheaper than purchasing thousands of CALs
- Internet-facing applications: Consumer-facing websites, mobile app backends, or public APIs cannot use CAL licensing (Microsoft's terms prohibit it). Per-core is mandatory
- Third-party SaaS integration: If your SQL instance serves multiple external customers or partners, CAL licensing quickly becomes impractical
- High-volume transaction systems: E-commerce platforms, financial trading systems, or real-time analytics platforms with unpredictable user counts
Server + CAL Licensing Model
How Server + CAL Works
The Server + CAL model requires two components:
- Server License: One per SQL Server instance (approximately £3,586 per 2-core pack, but often sold as a simpler "Server license" of ~£7,200 list for a single instance)
- Client Access License (CAL): One per user or device that accesses the database, priced at approximately £230 per device CAL or £175 per user CAL
The CAL type you choose matters:
- Device CAL: Covers any user on that device. Choose this if the same device is shared among multiple people or if the same person moves between devices
- User CAL: Covers any device the user accesses. Choose this if a single user uses multiple devices (mobile, laptop, desktop) to reach SQL
Most organisations choose Device CALs, as they're simpler to count and audit, though the cost per CAL is often slightly higher than User CALs.
CAL Economics in Practice
For a modest organisation with 500 employees needing database access:
- 1 Server License: ~£7,200
- 500 Device CALs at £230 each: £115,000
- Total: ~£122,200
That single server+CAL deployment costs more than the annual budgets of many IT departments. Scale this across 3 SQL instances (common for ERP, CRM, and BI), and you're looking at £366,600 in licensing costs. This is why per-core licensing often wins in large user environments—licensing 100 cores per-core is typically cheaper than licensing 1,500 device CALs.
CAL Limitations and Internet-Facing Restrictions
Microsoft's licensing terms explicitly forbid using CALs for internet-facing services. If your SQL Server instance directly serves external users (customers, partners, or public consumers), you must use per-core licensing. "Internet-facing" includes:
- Web applications (ASP.NET, PHP, Node.js) that query the database directly
- Mobile app backends (iOS, Android) connecting to SQL Server
- REST APIs or GraphQL endpoints backed by SQL Server
- Customer self-service portals or e-commerce platforms
- SaaS platforms where external users log in and generate queries
Internal applications serving only employees (ERP, CRM, HR systems) can use CAL licensing, as long as access is restricted to your corporate network or VPN and is authenticated only to your users.
SQL Server Edition Comparison
SQL Server comes in multiple editions, each with distinct features and licensing implications:
| Edition | Licensing Model | Key Features | Best For |
|---|---|---|---|
| Enterprise | Per-Core or Server+CAL | Advanced security, full high-availability, in-memory OLTP, advanced analytics, unlimited virtualisation on licensed host | Large, mission-critical systems; data warehouses; heavy transaction loads |
| Standard | Per-Core or Server+CAL | Basic replication, 128GB memory limit, 16 cores per instance max | Mid-market; departmental databases; line-of-business applications |
| Developer | Free (licensed for non-production only) | Full Enterprise feature set | Development, testing, learning; cannot be used in production |
| Express | Free (licensed for production) | 10GB database size limit, 1 core, 4GB memory | Small deployments, embedded applications, education |
Most enterprise deployments use Enterprise edition, as Standard's feature restrictions (especially the 16-core limit per instance, which was increased from 4 in recent versions) often eliminate it from consideration for production workloads. However, negotiating a mixed-edition agreement—Enterprise for critical systems, Standard for less-demanding workloads—can yield cost savings.
Virtualisation Rights: A Critical Advantage
Enterprise Edition: Unlimited Virtualisation
SQL Server Enterprise includes unlimited virtualisation rights on a licensed host. This means:
- If you license a physical server with 16 cores for SQL Server Enterprise, you can run unlimited SQL Server instances in unlimited virtual machines on that host—at no additional cost
- This applies to any hypervisor: Hyper-V, VMware vSphere, KVM, Xen, etc.
- This is a per-core license benefit—it applies to both per-core and Server+CAL licenses, but the value proposition changes based on model
For a cloud-native or DevOps team, this transforms SQL Server licensing economics. You can provision hundreds of SQL instances, each with a few hundred MB of memory, across a few licensed physical hosts—or across cloud hosts with Azure Hybrid Benefit (discussed below).
Standard Edition: Limited Virtualisation
SQL Server Standard allows only one virtual machine per license. If you deploy 10 SQL Server VMs, you need 10 Standard licenses. This severely limits Standard's appeal in virtualised environments and is one reason Enterprise dominates cloud and private cloud deployments.
Virtualisation and Your EA Negotiation
If your infrastructure strategy includes virtualisation (most do), ensure your Enterprise SQL licenses are explicitly included in your EA. Some organisations negotiate smaller per-core counts but lose virtualisation rights in the fine print—a costly mistake if you migrate to a cloud-first or hyperconverged infrastructure later.
Azure Hybrid Benefit for SQL Server
What Is Azure Hybrid Benefit?
Azure Hybrid Benefit (AHB) allows you to bring your on-premises SQL Server licenses to Azure and pay a discounted compute rate—typically 40–50% cheaper than pay-as-you-go (PAYG) pricing.
- Licensing Requirements: Your on-premises SQL licenses must be covered by Software Assurance (SA) or an active EA with per-core or Server+CAL licenses
- Applicable Workloads: SQL Server running on Azure VMs (IaaS). Cannot be used with Azure SQL Database or Azure SQL Managed Instance (unless using the Bring Your Own License option for Managed Instance, which has separate terms)
- Per-Core Conversion: One per-core SQL Server license covers up to 8 vCores of Azure VM compute. So 2 per-core licenses (4 cores) can cover an 8-vCore Azure VM
Cost Savings Example
A Standard_D8s_v3 Azure VM with SQL Server costs:
- PAYG (no AHB): ~£2.80/hour = £1,976/month or £23,712/year
- With AHB (2 per-core licenses): ~£1.40/hour = £988/month or £11,856/year
- Annual Savings: ~£11,856
If you have 10 such VMs, AHB saves £118,560/year. The business case for Azure migration can hinge on AHB; always factor it into cloud cost models.
Critical AHB Rules
- You must assign your on-premises licenses to Azure VMs. You cannot use the same license simultaneously on-premises and in Azure
- AHB eligibility is tied to Software Assurance. Once SA expires, AHB eligibility ends (though you can still run the software—you just pay PAYG rates)
- AHB can be combined with Azure Reserved Instances for additional 15–30% discounts
Software Assurance and Licence Mobility
What Software Assurance Covers
Software Assurance (SA) is an annual or three-year agreement that extends beyond the base license purchase. For SQL Server, SA includes:
- Licence Mobility: The right to move licenses to a third-party hosting provider (e.g., a managed service provider or cloud provider other than Microsoft). Without SA, you cannot reassign licenses to hosted environments
- Disaster Recovery (DR) Rights: You can maintain passive standby replicas of your SQL instance for free—no additional licenses required. This is invaluable for high-availability setups
- Free Passive Secondaries: Related to DR, but worth highlighting: AlwaysOn Availability Group secondaries used solely for failover do not require additional licensing
- Azure Hybrid Benefit: As covered above, SA is required to use AHB
- Version Upgrades: Included in SA, allowing you to upgrade to newer SQL Server versions without repurchasing licenses
SA Negotiation in Your EA
SA is typically 25–30% of the base license cost per year. For a £100,000 SQL Server deployment, SA might add £25,000–£30,000 over three years. However, the DR rights alone (passive secondaries at no cost) can save more than SA's cost, especially for critical systems.
Negotiate SA as part of your overall EA. If your business requires multi-region HA or frequent version upgrades, SA is mandatory. If you have no DR strategy, you might defer SA initially, though this is risky for critical databases.
Common Audit Traps and Licensing Mistakes
Trap 1: Internet-Facing CAL Deployments
The most frequent SQL Server audit failure we see: an organisation licensed a web application's SQL backend on CAL, assuming all users were "internal" because the app ran on an internal server. Microsoft discovered that external customers connected via the internet, invalidating the CAL license entirely. The organisation faced £500,000+ in true-up costs.
Rule: If any external entity (customer, partner, or public user) can query your SQL instance, it's internet-facing. Use per-core.
Trap 2: Under-Counting Cores on Multi-Socket Servers
A common mistake: licensing a dual-socket server but counting only the cores in one socket. Modern processors have 10, 12, 16, or more cores per socket. A quad-socket server with 16 cores per socket requires 32 two-core packs—64 licenses—not 16.
Microsoft audits are ruthless about this. If you're one core short across all instances, you're non-compliant.
Trap 3: VM Sprawl and Virtualisation Undercounting
Teams provision VMs ad hoc and lose track of SQL instances. A DevOps team might spin up 20 SQL Server test instances on a per-core licensed host, thinking the host license covers them (it does). But when audited, the organisation cannot prove that all VMs were running on licensed hosts, and Microsoft charges for the untracked instances.
Mitigation: Maintain a live inventory of all SQL Server instances (on-premises and cloud) mapped to licensing. Update it monthly.
Trap 4: Passive Secondaries Without SA
An organisation sets up AlwaysOn Availability Groups with a passive secondary for HA, assuming the secondary doesn't need licensing (true, but only with SA). Without SA, every replica is a separate licensed instance.
Result: An organisation with a £20,000 SQL deployment discovers it needed £40,000 (two instances) or must delete the secondary. This often surfaces during EA renewal audits.
Trap 5: Failing to Adjust CAL Count During Restructures
When organisations merge, divest, or restructure, the user base changes. If you licensed 1,000 Device CALs three years ago but now have 1,500 employees, you need 500 additional CALs. Many organisations don't update their inventory and face compliance gaps during renewal.
Best Practice: Audit your CAL count annually against actual headcount or device count. Flag any growth to your license management team.
Negotiation Tactics for SQL Server in the EA
Bundle SQL Server with Windows Server and Other Products
Microsoft values bundling. If you're negotiating per-core Windows Server and SQL Server together, you often receive higher discounts than buying them separately. Propose an enterprise deal that includes:
- Windows Server per-core licenses
- SQL Server per-core licenses
- Office/Microsoft 365 seats
- Dynamics/other applications
Microsoft's sales team has more flexibility to discount when the total contract value is large and bundled across products.
True-Up Exposure and Advance Purchases
EAs typically include a true-up clause: if you purchase fewer licenses than you actually deployed, you owe the difference at renewal or mid-term. If your SQL Server growth is unpredictable, buy a conservative initial quantity and plan to true-up rather than over-licensing.
Conversely, if you know growth is coming, purchase upfront and get a lower blended rate than true-up pricing. The difference can be 10–20%.
Right to Downgrade and Version Flexibility
Negotiate the right to downgrade SQL Server Enterprise to Standard (or vice versa) without penalty during the EA term. Business needs change; workload consolidation or cost pressures might shift your edition mix. A flexible agreement lets you adapt without contractual friction.
Also clarify version support: if you're running SQL Server 2019, will Microsoft force you to upgrade to 2022 mid-contract, or can you stay on 2019? Forced upgrades can disrupt operations and introduce compatibility risks.
Cloud Optimisation and License Portability
If you're planning an Azure migration, negotiate terms that make AHB seamless. Some EAs include restrictions that complicate AHB eligibility. Ensure:
- All SQL Server licenses have SA or are eligible for AHB under your specific EA terms
- You can reassign licenses to Azure without penalty
- Passive replicas for DR/HA are explicitly covered as free (SA requirement)
Related Insights and Next Steps
SQL Server licensing is one lever in a broader Microsoft cost optimization strategy. Many organisations miss savings by treating SQL, Windows, and Azure independently. Consider reading our guides on Windows Server licensing to understand how per-core costs compound, and explore Azure Hybrid Benefit negotiation tactics if cloud migration is in your roadmap.
For audit preparedness, our guide to Microsoft Software Asset Management (SAM) audits provides a framework for inventory, compliance, and negotiation when auditors arrive.
If you are planning a significant SQL Server deployment or renewal, we recommend a cost model review. The difference between the model you choose and the one you should have chosen often justifies a dedicated analysis.
SQL Server licensing—per-core vs. Server+CAL—is a binary choice with massive financial consequences. Per-core wins for large user bases and internet-facing systems; Server+CAL wins for small, internal deployments. Azure Hybrid Benefit can swing the business case toward cloud migration. Software Assurance unlocks disaster recovery and license flexibility. And virtualisation rights in Enterprise edition can make or break cost models in virtualised environments. Get the model right, and you save hundreds of thousands. Get it wrong, and audits become painful.