SQL Server 2025 Licensing Explained: Per Core vs Server + CAL, Standard vs Enterprise, Virtualization, and Azure Hybrid Benefit
SQL Server licensing has two models, two production editions and three places to count cores: the physical host, the virtual machine, or the Azure VM you bring the license to. Get the counting rule right and the rest is arithmetic that our calculators do at Microsoft's list price. Get it wrong and the difference shows up at true-up.
The two models: per core and Server + CAL
Per core licenses the instance by the cores it runs on. Licenses are sold in two-core packs, every core in the operating system environment is licensed, and there is a minimum of four core licenses per OSE, so a two-vCPU virtual machine still needs four. Nobody who connects needs a Client Access License. Per core is the only model for Enterprise edition in new agreements and the compliant model for any database whose user population you cannot count, such as a public website.
Server + CAL licenses the instance once and then licenses every user or device that accesses it, directly or through an application in between. Microsoft calls that indirect access multiplexing, and a web or application tier does not reduce the CAL count. For SQL Server 2025 this is a Standard edition choice: Microsoft's edition documentation states that Enterprise under Server + CAL is not available for new agreements and, where it survives from older ones, is limited to 20 cores per instance.
The decision rule is short: a small, countable population on a small server favors Server + CAL; many cores, uncountable users or Enterprise features mean per core. Our SQL Server licensing calculator works out the break-even user count from live list prices, and the CAL calculator counts SQL CALs beside the Windows Server CALs the same users already need; our CAL guide covers that side.
Standard or Enterprise: what the edition changes
Editions decide features and scale, not the licensing model. From Microsoft's SQL Server 2025 edition documentation, the lines that decide most purchases:
- Compute and memory. Standard uses the lesser of 4 sockets or 32 cores per instance (24 cores in SQL Server 2022 and earlier) and 256 GB of buffer pool; Enterprise uses the operating system maximum. These are engine limits, not licensing limits.
- High availability. Standard gets two-node failover cluster instances and basic availability groups (two replicas, one database); Enterprise gets full availability groups with up to eight secondaries, online index operations and online page restore.
- Security. In 2025, transparent data encryption, Always Encrypted with secure enclaves, ledger, row-level security and the vector and AI features are in Standard as well as Enterprise.
- Virtualization rights. Enterprise offers unlimited virtualization for customers with Software Assurance; Standard does not.
Express is available at no charge, limited to the lesser of one socket or four cores and a 50 GB database. The Enterprise Developer and Standard Developer editions are licensed for development and test, not production; Evaluation runs for 180 days; Web edition is not offered for SQL Server 2025.
Counting cores under virtualization: VM, host, or unlimited
Microsoft's Azure Arc licensing documentation describes three ways to license SQL Server on virtualized hardware; they apply whether or not the server touches Azure.
- By virtual cores, per VM. License the virtual cores allocated to each VM that runs SQL Server: two-core packs, four-core minimum, Standard or Enterprise.
- By physical cores, without VMs. License all physical cores of a host that runs SQL Server directly on the operating system, at the highest edition installed on it.
- By physical cores with unlimited virtualization. License every physical core of the host with Enterprise edition under active Software Assurance or a SQL Server subscription, and run any number of VMs with any number of instances. Standard cannot do this, and neither can a license without Software Assurance. Under Azure Arc the physical-core license resource has a minimum size of 16 physical cores.
The break-even is mechanical: once the virtual cores you would license across VMs exceed the host's physical cores, and you are on Enterprise anyway, licensing the host wins. Containers are governed by Microsoft's SQL Server licensing guide, which we could not open from here; confirm its current wording before you count them.
Two facts for buyers in the CSP channel. A perpetual SQL Server license bought through CSP carries no Software Assurance, so it brings no unlimited virtualization, no license mobility and no Azure Hybrid Benefit. A one- or three-year SQL Server subscription license includes the right to run current versions while active and is the license that Azure Hybrid Benefit and unlimited virtualization accept. The calculator prices both.
Pay-as-you-go through Azure Arc
SQL Server 2022 and 2025 can also be licensed by the hour. Connect the server to Azure Arc, install the Azure extension for SQL Server, set the license type to pay-as-you-go, and Standard or Enterprise usage is metered hourly to your Azure subscription. Microsoft's conditions: hourly charges apply only while SQL Server is running and the machine is online; connectivity can drop for up to 30 consecutive days without affecting billing, after which the subscription expires; and Enterprise can subscribe at the host level for unlimited virtualization.
The extension carries three license types, pay-as-you-go, license with Software Assurance, and license only, and the type you pick is an attestation: an instance on Server + CAL must be set to license only even with Software Assurance, and an Azure subscription managed through a CSP partner needs consent to recurrent billing first. The meter is Microsoft's, billed to your Azure subscription; our Azure Arc guide covers what Arc itself costs.
The Azure Hybrid Benefit hook, and when the calculators answer the question
Azure Hybrid Benefit lets you allocate SQL Server core licenses with active Software Assurance, or subscription licenses, to SQL Server on an Azure VM, Azure SQL Managed Instance or Azure SQL Database, and pay the base compute rate instead of a license-included rate. Only core-based licenses qualify; Server + CAL with Software Assurance gets license mobility to an Azure VM but not the rest of the benefit. On Azure SQL one Enterprise core covers four General Purpose vCores while one Standard core covers one; Microsoft allows 180 days of dual use for the migration; and on an Azure VM the benefit brings one passive high-availability replica and one disaster-recovery replica without a license charge. Our Azure Hybrid Benefit guide covers the mechanics.
So when do the calculators answer the question outright? When you know the cores, the edition, the user count if Standard, and whether the workload runs all day. The SQL Server licensing calculator prices per-core perpetual, per-core subscription and Server + CAL from the live catalog, then sets them beside an Azure VM with the benefit, a license-included Azure VM, AWS license-included, and Azure SQL with and without the benefit; license figures are Microsoft's list prices, and cloud compute figures are labeled samples you replace with your own quote.
What the calculators cannot answer is which target your application can move to; our SQL Server to Azure Migration Assessment sizes and licenses the target before quoting the move. SQL Server 2016 left support on 14 July 2026 and SQL Server 2017 follows on 12 October 2027; our 2016 end-of-support guide lists the paths.
Frequently asked questions
Do I still need SQL CALs if I license per core?
No. Per core covers any number of users and devices. They still need a Windows Server CAL for the server itself unless a Microsoft 365 seat covers it under the Product Terms.
How many licenses does a two-vCPU virtual machine need?
Four, sold as two two-core packs; the minimum applies per operating system environment.
Can I buy Enterprise edition with Server + CAL?
Not in a new agreement. Where it survives from an older one it is limited to 20 cores per instance; per core is the Enterprise model.
Does Standard's 32-core limit mean I only license 32 cores?
No. It is an engine limit on what one instance uses; licensing follows the cores in the OSE or on the host.
Is a CSP perpetual license eligible for Azure Hybrid Benefit?
No, because it has no Software Assurance. A SQL Server subscription license through CSP is eligible, as are volume-licensing licenses with active Software Assurance.
Sources
- Microsoft Learn: Editions and supported features of SQL Server 2025; Compute capacity limits by edition of SQL Server; Manage SQL Server license and billing options (SQL Server enabled by Azure Arc); Change the license model for a SQL virtual machine in Azure; Pricing guidance for SQL Server on Azure VMs; Azure Hybrid Benefit for Azure SQL Database and SQL Managed Instance
- Microsoft Learn training module: Optimize costs using Azure Hybrid Benefit (the four-core minimum per VM)
- IT Partner: SQL Server licensing calculator rule table; Client Access Licenses in 2026; SQL Server 2016 End of Support; deadlines calendar
Microsoft's SQL Server licensing guide and the Product Terms were not opened; where a rule lives only there, the text says so.
| Question | Per core (Standard or Enterprise) | Server + CAL (Standard only in new agreements) |
|---|---|---|
| What you license | Every core in the OSE, in two-core packs, four minimum | One server license per OSE plus a CAL for every user or device, including access through an application |
| Who may connect | Anyone | Only licensed users and devices |
| Typical fit | Uncountable users, many cores, Enterprise features | A small, countable population on a small server |
| Virtualization | Per VM by virtual cores, or an Enterprise host with SA or subscription for unlimited VMs | Per instance; the CALs cover the population |
| Azure Hybrid Benefit | Yes, with Software Assurance or a subscription license | No; license mobility only, with Software Assurance |
Key takeaways
- Per core: two-core packs, a four-core minimum per OSE, no CALs. Server + CAL: Standard only, and every user or device counts, even through an application.
- Edition sets engine limits and features, not the licensing model; only Enterprise with Software Assurance or a subscription gets unlimited virtualization.
- Under virtualization you license virtual cores per VM, all physical cores of a host, or physical cores with unlimited virtualization on Enterprise.
- A CSP perpetual license carries no Software Assurance; a CSP subscription license is what Azure Hybrid Benefit and unlimited virtualization accept.
- Azure Arc adds an hourly pay-as-you-go meter for SQL Server 2022 and 2025, billed to your Azure subscription.
Run the SQL Server licensing calculator with your cores, edition and user count before you ask anyone for a quote, and the CAL calculator if Server + CAL is in play. If the answer depends on where the database will live, the SQL Server to Azure Migration Assessment sizes and licenses the target for a fixed $950 and returns a written quote; if the question is what you already own, the Windows Server and SQL Server Licensing and True-Up Advisory reconciles it.
Questions this article didn’t answer?
Thirty minutes with Mike — our CEO, not a sales rep. Bring the hard version of the question.