Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Review

SQL Server Core Licensing vs Server Plus CAL: Which Model Wins for You?

11 min read Updated October 5, 2026 Microsoft Licensing Guides

Fix it now

Per core charges for the hardware and ignores users; Server plus CAL charges for the instance plus every user or device and ignores the hardware. Server plus CAL is available on Standard only, Enterprise is per core only, and the multiplexing clause means pooling connections behind a service account does not reduce the CAL count.

  1. Buy Server plus CAL if the connecting population is internal, countable and stable, and the server is large relative to it.
  2. Buy per core if anything outside your organisation reaches the database. You cannot enumerate the public, so you cannot license them individually.
  3. Buy per core if you need Enterprise for availability groups or scale. Microsoft sells Enterprise under the per-core model only.
  4. Buy per core on a small virtual machine even with many users: the minimum is four core licences per virtual OSE, which is often less than a server licence plus fifty CALs.
  5. Do not assume a web tier or integration layer reduces the count. Microsoft’s multiplexing clause says pooling does not reduce the licences needed.
  6. Buy neither for development or test. Developer edition is free for non-production use.

Core licences are sold in two-core packs. The minimum is four licences per physical processor when licensing hardware, and four per virtual OSE when licensing a virtual machine.

If external access or the Enterprise requirement has already decided it, stop here. Below is how to run the comparison on your own quote, and the clauses that quietly remove Server plus CAL as an option.

Why it happens

The two models are priced on completely different things, which is why one of them is usually much cheaper for any given deployment and why the answer flips so sharply between deployments.

Per-core licensing counts physical cores. Microsoft’s Product Terms require a number of licences equal to the number of physical cores, subject to a minimum of four licences per physical processor. Licence a virtual machine instead and you count the virtual cores assigned to it, subject to a minimum of four licences per virtual OSE. Either way, nothing in the count depends on how many people use the database. Licences are sold in two-core packs.

Server plus CAL counts people. You buy one server licence for each running instance and then a Client Access Licence for every user or device that accesses the server software. These are not concurrent licences, so forty staff taking turns at ten terminals need forty user CALs or ten device CALs, and you take whichever count is smaller. The size of the box is free under this model, which is the whole asymmetry.

Something outside the organisation reaches the database

You have this one if A customer portal, a public website, a mobile app, a partner extranet, an API anyone can call.

  1. Per core, without further analysis. Under Server plus CAL every user or device accessing the server software needs a CAL, and you cannot enumerate and license an anonymous population.
  2. One public component is enough to decide the whole instance. You cannot license part of an instance one way and part the other.
  3. This is the most expensive mistake in the comparison, because CALs bought for a deployment that needed per core are not refunded by discovering the error later.

The design needs Enterprise edition

You have this one if Always On availability groups, unlimited virtualisation, or scale past Standard’s ceiling of four sockets or 32 cores and 256 GB of buffer pool.

  1. Enterprise is sold under the per-core model only. Microsoft’s licensing guidance lists Server plus CAL against Standard alone.
  2. Once Enterprise is required the user count stops mattering entirely, so stop counting people and start counting cores.
  3. With active Software Assurance and Enterprise licensed by physical core, you may run any number of instances in any number of operating system environments on the licensed server. That is the case where per core is not only mandatory but cheap.

Somebody has designed the users out of the count

You have this one if A quote assumes a handful of CALs because staff reach the data through a web application, a reporting portal or an integration service using one credential.

  1. Microsoft’s Product Terms state that any method a customer uses to pool connections, to reduce the number of devices or users that directly or indirectly access or use a product, or to access data the product processes or generates, does not reduce the number of licences needed.
  2. The service account is not the licensed entity. The people or devices whose work it performs are.
  3. A design that hides two hundred staff behind one connection still needs licensing for two hundred, so treat any quote that shrinks with an architecture diagram as wrong.

One more clause belongs in the comparison before you price anything. Failover and disaster recovery rights are not automatic under either model: Microsoft requires active Software Assurance or subscription licences for them, and under Server plus CAL that means Software Assurance on the server licence and on the CALs. A passive replica you assumed was free is a real line on the quote.

Full reference

The two models, side by side

Dimension Per core Server plus CAL
What you pay for Physical cores of the host, or virtual cores of the instance One licence per running instance, plus one per user or device
Published minimum 4 licences per physical processor; 4 per virtual OSE Not applicable
Pack size Two-core packs Server licence and CALs bought individually
Effect of a bigger server Direct cost increase None
Effect of more users None Direct cost increase
Users you cannot enumerate Fully supported Not workable; every user or device needs a CAL
Editions available Standard and Enterprise Standard only
Unlimited virtualisation Enterprise, licensed by physical core, with Software Assurance Not available
Failover and disaster recovery rights Software Assurance or subscription licences required Software Assurance required on the server licence and the CALs
Reassignment between servers Freely within a server farm with Software Assurance or subscription; between farms, not within 90 days Same 90-day rule applies

Running the comparison on your own quote

  1. Count physical cores in the host, or virtual cores of the instance if you are licensing at virtual machine level, then apply the minimum of four licences per physical processor or per virtual OSE and round up to whole two-core packs.
  2. Count distinct users, and separately count distinct devices. Take the smaller figure as the CAL count.
  3. Add a growth allowance to the user count only. CALs are the side of the model that inflates as the company hires; cores do not.
  4. Price core licences for the first figure, and one server licence per running instance plus CALs for the second.
  5. Add Software Assurance to whichever side needs it, including on the CALs if you want failover rights under Server plus CAL.
  6. Check whether any connection originates outside your organisation. One customer-facing component removes Server plus CAL from the comparison entirely.

The crossover is entirely a function of your quoted prices, so the arithmetic above is the article’s actual answer. What is durable is the shape: Server plus CAL wins where the box is large and the population is small and internal, and per core wins where the population is large, unknown or external, or where the machine is small.

Mixing, and what cannot be mixed

An instance is licensed one way or the other. You cannot licence part of an instance by core and part by CAL, and you cannot make a Server plus CAL instance compliant by adding a few core licences to cover the external users. Different servers in the same organisation may use different models, which is normal in an estate that has grown, but each instance has one answer.

CALs themselves are portable across servers in the way Windows Server CALs are: a CAL permits access to the licensed servers you run, so the same CAL does not need buying again for each instance the user reaches. Each of those instances still needs its own server licence. Confirm the version rule for your CALs against the Product Terms for the release you are buying, because that is the detail resellers most often get wrong on a mixed-version estate.

Virtualisation, and where the minimum bites

Two routes exist. Licensing the physical host by core covers everything running on it, and with Enterprise plus Software Assurance covers any number of instances in any number of operating system environments. Licensing individual virtual machines counts virtual cores with a floor of four licences per virtual OSE, which is why a two-vCPU virtual machine costs the same as a four-vCPU one and why densely packed hosts eventually favour host-level licensing.

Reassignment matters on clusters. Microsoft permits reassigning licences to any of your licensed servers within the same server farm as often as you need where the licences are subscription licences or carry active Software Assurance. Between farms, reassignment is not permitted on a short-term basis, which Microsoft defines as within 90 days of the last assignment. If virtual machines move between hosts automatically, that distinction is the one to get right before you buy.

One change worth knowing about

Power BI Report Server now comes with both Enterprise and Standard without requiring Software Assurance, where previously it was an Enterprise plus Software Assurance benefit. If reporting was going to push you toward Enterprise, price Standard again first.

When a licence is the actual fix

For an internal system with a countable user base, SQL Server 2025 Standard core licences are frequently not the cheaper option, and Arco will price both models rather than assuming one. Send us the socket and core count of the host or the vCPU count of the virtual machine, the number of distinct people and distinct devices that connect, and whether anything outside your organisation reaches the database. We will come back with the per-core figure and the Server plus CAL figure side by side on your own numbers, including any Software Assurance you need for failover rights. Where a customer-facing component makes per core mandatory, we will tell you that before you have paid for CALs you cannot use.

Questions people ask about this

Can I mix the two models on the same server?

Not within one instance. An instance is licensed by core or by Server plus CAL, never partly by each, and you cannot bolt core licences onto a CAL-licensed instance to cover external users. Different instances in the same organisation may use different models, which is common in an estate that has grown by acquisition.

Does a service account count as one user?

No. Microsoft’s Product Terms state that any method used to pool connections, or to reduce the number of users or devices that directly or indirectly access a product, does not reduce the number of licences required. The account is not the licensed entity; the people or devices whose work it performs are. An integration service connecting with one credential on behalf of two hundred staff needs licensing for those two hundred.

Is per core always more expensive for small user counts?

No, and it is worth actually checking. The floor is four core licences per virtual OSE, so a lightly provisioned virtual machine can be licensed by core for less than a server licence plus fifty CALs. Divide the per-core figure on your quote by the cost of one CAL to see how many CALs the core route is worth, then compare that with your headcount.

Do I get a free passive replica?

Only with active Software Assurance or subscription licences. Microsoft states that licences without Software Assurance, and non-subscription licences, do not include disaster recovery or high availability rights. Under Server plus CAL, failover rights require Software Assurance on the server licence and on the CALs. Budget for it rather than discovering it during a failover test.

What if we grow past Standard?

Enterprise is per core only, so the user count stops mattering the moment you need it. Standard’s ceiling in SQL Server 2025 is the lesser of four sockets or 32 cores with 256 GB of buffer pool, and Always On availability groups are Enterprise-only. If either is on the roadmap, price the per-core route now so the eventual move is a quantity change rather than a model change.

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Review E3 Plus Add-Ons or Straight to E5? Building the Cheaper Security Stack Review Microsoft 365 E3 vs E5: What the Security and Voice Add-Ons Are Worth Review Counting Cores Correctly: Server Licence Minimums That Catch People Out Review Windows 11 Pro vs Pro for Workstations: Who Actually Needs ReFS?
โ† Back to Knowledge Base