SQL Server Licensing Explained: Cores, CALs & Editions

SQL Server Licensing in 2026: Official Reference Points

Software licensing audits frequently uncover compliance gaps caused by reliance on third-party distributor quotes rather than Microsoft's formal licensing documentation. Microsoft maintains updated official guidance for SQL Server 2025, which is the current primary reference point for SQL Server licensing going forward, while SQL Server 2022 documentation remains relevant for environments still running 2022 and for specific licensing scenarios described in those materials. While distributors frequently market licenses with bundled services, Microsoft publishes licensing rules and baseline product information directly through its official portals.

For UK IT directors and procurement leads, commercial licensing routes dictate both purchase price and long-term cost volatility. Most UK commercial and public-sector organisations procure SQL Server licences either via an Enterprise Agreement (EA) or Microsoft Products and Services Agreement (MPSA) through a tier-1 UK Licensing Solution Provider (LAR/LSP), or via the Cloud Solution Provider (CSP) channel for monthly or annual subscriptions. A significant commercial consideration for UK buyers is Microsoft's periodic local-currency pricing alignments: Microsoft adjusts UK pricing in sterling against USD exchange rates, meaning multi-year renewals and true-ups can experience sharp inflationary jumps. Furthermore, Microsoft UK compliance audits—frequently conducted on Microsoft's behalf by firms like KPMG or Deloitte—scrutinise multiplexed web front-ends, virtual machine mobility across VMware or Hyper-V clusters, and unlicenced standby nodes, turning documentation oversights into immediate commercial true-up liabilities.

Understanding the Core Models: Per Core vs Server + CAL

Microsoft provides two distinct licensing paths for SQL Server: the Per Core model and the Server + Client Access License (CAL) model. The Per Core model licenses underlying compute capacity—either physical processor cores or allocated virtual cores—enabling unlimited internal and external user access without seat tracking. In contrast, the Server + CAL model requires a single server licence for each operating system environment (physical or virtual) plus access licences for every individual user or device connecting to the database.

Edition availability is strictly partitioned between these two models. SQL Server Standard can be licensed under either Per Core or Server + CAL, giving organisations flexibility based on their compute-to-user ratio. SQL Server Enterprise, however, is licensed exclusively under the Per Core model to reflect its high-scale clustering, advanced security, and enterprise analytical workloads.

For Per Core deployments, Microsoft sells licences in two-core packs and enforces a hardware baseline: every physical core on each processor must be licensed, with an absolute minimum of four core licences per physical processor. A server equipped with a single dual-core CPU still requires four core licences (two 2-core packs). When sizing hardware, this four-core per-socket minimum represents an unavoidable cost floor.

• •Server + CAL model: Available for SQL Server Standard edition; Enterprise edition uses Per Core licensing only.
• •Per Core model: Available for both Standard and Enterprise editions.
• •Physical core rule: All physical cores must be licensed, with a minimum of 4 core licenses per processor.
• •Access licensing: CALs can be assigned per individual User or per individual Device and are required for each user or device that has direct or indirect access to a SQL Server instance licensed under the Server + CAL model.

CAL Mechanics: User CALs, Device CALs, and Indirect Access

When an organisation selects Server + CAL licensing for Standard edition, access governance must be mapped across all clients. Microsoft distinguishes between User CALs and Device CALs. A User CAL grants one named person access to the database from any endpoint, making it ideal for staff utilising laptops, smartphones, and desktop systems. A Device CAL permits an unlimited number of operators to share a single physical endpoint, which represents a standard deployment pattern on factory floors, call centres, or reception desks.

A critical advantage of the Server + CAL model is broad access scope within the organisation: once a SQL CAL is properly assigned to a user or device, that CAL allows access to any properly licensed SQL Server in the organisation’s environment, regardless of the underlying platform or SQL Server edition or version. However, administrators must account for indirect access (multiplexing). When intermediary applications, web front-ends, or automated batch processes sit between users and the database engine, CALs are still legally required for every user or endpoint pooling requests upstream, unless licensed under the Per Core model.

Virtualisation and Container Licensing Rules

Virtualising SQL Server introduces specific regulatory conditions that diverge depending on whether an organisation deploys Server + CAL or Per Core licensing. Under the Server + CAL model for SQL Server Standard edition, an organisation must acquire a distinct server licence for each virtual machine (VM) or container hosting a SQL Server instance, in addition to maintaining appropriate CAL coverage for all upstream access.

Under the Per Core model, the rules depend heavily on Software Assurance (SA) or active subscription licensing. Beginning with SQL Server 2022 and sustained under SQL Server 2025 guidance, licensing an individual virtual OSE (such as an individual VM or container) under Per Core terms is only permitted if the customer holds active subscriptions or licenses with active Software Assurance. Customers without active SA cannot selectively license virtual cores for an individual VM.

When virtual cores are licensed under an active subscription or SA, Microsoft enforces a minimum allocation of 4 core licenses per VM or container. Alternatively, organisations can license all physical cores on a server under the Per Core model, subject to Microsoft’s minimums. With eligible Enterprise licences and active Software Assurance or subscription, Microsoft’s guidance allows customers to run multiple SQL Server instances across physical and virtual OSEs on a server where all physical cores are licensed, rather than enforcing a one‑VM‑per‑core limit; instance density is governed by the edition’s specific use rights rather than a hard VM‑per‑core cap.

Software Assurance Benefits and Cloud Mobility

Software Assurance (SA) functions as far more than a version-upgrade contract; it provides mobility rights, high-availability failover allowances, and critical virtualisation flexibility. In virtualised environments, maintaining active SA or a subscription avoids the costly requirement to license every physical host core, making it an essential operational component of any dynamic hypervisor cluster.

Furthermore, active SA grants license mobility rights and Azure Hybrid Benefit (AHB). For UK organisations weighing on-premises Per Core licensing against cloud alternatives, managed PaaS solutions such as Azure SQL Managed Instance (SQL MI) bundle compute and licensing into an hourly operational cost, while Azure Arc enables pay-as-you-go (PAYG) monthly consumption for on-premises hardware without upfront multi-year commitments. In on-premises and hybrid architectures, SA also covers secondary disaster recovery and failover instances without additional core licensing, provided the passive instances meet Microsoft's qualifying terms. Database engineering teams should evaluate these cloud and hybrid consumption models alongside physical host quotes when they spec a SQL database server, balancing fixed capital investment against scalable operational expenditure.

• •Individual VM per-core licensing: Exclusively available with active SA or subscription licenses.
• •High availability rights: Covers passive secondary failover instances when active SA is maintained.
• •Cloud mobility: Facilitates flexible workload migrations across hybrid infrastructure tiers.
• •Physical host licensing: Licensing all physical cores on a host under the Per Core model provides rights to run SQL Server instances across containers and VMs on that host, with the number of allowed OSEs and instances governed by the edition’s use rights and the total core licences assigned.

Break-Even Dynamics: Per Core vs Server + CAL

The economic threshold between Server + CAL and Per Core licensing hinges directly on compute volume versus accessing user count. To calculate the crossover point, organisations must evaluate compute capacity against accessing identities using current list pricing. Microsoft sells Per Core licences in two-core packs. Indicative commercial list prices (open perpetual licences without Software Assurance) provide a standard baseline: | Licence SKU / Component | Indicative US List (MSRP) | Indicative UK List (excl. VAT) | Metric / Sizing Unit | |---|---|---|---| | SQL Server Standard (2-Core Pack) | ~$3,945 | ~£3,200 | 2 physical or virtual cores (4-core min.) | | SQL Server Enterprise (2-Core Pack) | ~$15,123 | ~£12,250 | 2 physical or virtual cores (4-core min.) | | SQL Server Standard Server Licence | ~$1,025 | ~£830 | Per physical or virtual instance | | SQL Server User or Device CAL | ~$240 | ~£195 | Per individual user or endpoint | *Note: UK sterling figures reflect direct conversions from standard commercial USD price lists; actual billing varies based on partner margins, Enterprise Agreement bandings, and Microsoft exchange-rate adjustments.*

Consider a concrete worked example: a mid-tier database running on a dual-socket server with 16 physical cores total (8 cores per CPU): - **Per Core route (Standard):** Sizing 16 cores requires eight 2-core packs. At ~£3,200 per pack, total licensing is approximately **£25,600**, granting unlimited internal and external user access. - **Server + CAL route (Standard):** The base server instance licence costs ~£830. Adding 30 user CALs at ~£195 each (£5,850) yields a total cost of **£6,680**—a 74% upfront saving compared to Per Core. - **The Crossover Point:** Setting both options equal (£830 + [CAL count × £195] = £25,600) yields a break-even point of **approximately 127 users**. If the system supports fewer than 125 internal users or devices, Server + CAL is significantly cheaper. Once user counts exceed 130—or if an unauthenticated web portal introduces uncounted indirect access—Per Core becomes both more economical and legally compliant. Note that for Enterprise edition, Server + CAL is not an option; that same 16-core physical server would require £98,000 in Enterprise Per Core licences.

Audit Compliance and Hardware Sizing Pitfalls

Database administrators must align server hardware configurations with software licensing constraints. Deploying high-core-count processors in a virtual host cluster can trigger massive unexpected liabilities if a database instance is migrated across unconstrained nodes without proper SA mobility or comprehensive host core coverage.

To maintain rigorous compliance during a Microsoft audit, UK enterprises should maintain centralized license registers, clearly delineate passive disaster recovery instances, and evaluate indirect access vectors. Teams assessing complex infrastructure changes can model their hypervisor configurations using a Microsoft licensing calculator or review broader platform choices against Windows Server Standard vs Datacenter licensing documentation.

Sources

Every figure in this article traces to the sources below.

• •Microsoft — SQL Server 2025 Licensing Guidance
• •Microsoft — Product Licensing Terms
• •Microsoft — SQL Server Licensing Guide Reference
• •Licenseware — Microsoft SQL Server Licensing Guide
• •Microsoft — SQL Server Pricing Reference