Licensing & Buying Guides
SQL Server Licensing Explained: Per Core vs Server + CAL — Which Model Saves You Money?
Quick Answer
The short version of SQL Server licensing per core vs CAL: Per-Core licensing charges by physical processor cores (sold in packs of two, with a 4-core minimum per processor) and covers an unlimited number of users or devices — the right call for internet-facing apps or large, unpredictable user bases. Server + CAL licensing charges one server license plus one Client Access License per named user or device, and it’s usually the cheaper path for a small, fixed team of known users on SQL Server Standard Edition only — Enterprise Edition is sold per-core exclusively.
SQL Server Licensing Per Core vs CAL: Side-by-Side Comparison
Here’s the whole decision in one table, based on how Microsoft defines the two models.
| Factor | Per-Core Licensing | Server + CAL Licensing |
|---|---|---|
| How it’s counted | By physical processor cores, sold in 2-core packs | 1 server license + 1 CAL per named user or device |
| Minimum requirement | 4 core licenses per physical processor, even on lower-core CPUs | 1 server license per running SQL Server instance, plus a CAL for every user/device that connects |
| Who it fits | Internet-facing apps, e-commerce sites, or any workload with many or anonymous/unknown users | Small offices with a fixed, known headcount (e.g., 10–25 named staff) |
| Cost dynamics | Fixed cost regardless of how many users connect — scales with hardware, not headcount | Cost climbs directly with every added user or device |
| Standard vs Enterprise eligibility | Available on both Standard and Enterprise Editions | Standard Edition only — Enterprise Edition is per-core exclusively |
| External/anonymous access | Included — no extra CALs needed for outside users | Not permitted without an External Connector license |
| Virtualization | Scales cleanly to VMs; Enterprise Edition with Software Assurance supports unlimited virtualization | Each VM instance still needs its own server license and CALs still apply per user/device |
How Per-Core Licensing Works
Per-Core is the “pay for the hardware, not the headcount” model. You license every physical core on the server that will run SQL Server, and once that’s done, an unlimited number of users and devices — inside or outside your firewall — can connect without buying anything else.
Core Packs and the 4-Core Minimum
Two rules govern the math. SQL Server core licenses are sold in packs of two, and Microsoft enforces a minimum of four core licenses per physical processor, regardless of actual core count. A dual-processor server with 8 cores per socket requires 16 licenses (8 × 2), purchased as eight 2-core packs. These rules come straight from Microsoft’s core-based licensing guidance and apply regardless of reseller or edition.
Who Per-Core Licensing Is Built For
Per-Core makes sense when the number of people or systems touching your database is large, unpredictable, or not worth tracking — think customer-facing web apps, SaaS backends, or e-commerce databases. Because the license is tied to hardware rather than connection count, adding 10 or 10,000 more users costs nothing extra.
How Server + CAL Licensing Works
Server + CAL flips the math: you buy one relatively inexpensive server license to run the software, then pay per person (or per device) who actually connects to it.
What a CAL Covers (User CAL vs Device CAL)
A Client Access License is required for every user or device that accesses the SQL Server instance. You choose a User CAL (one person, any device) or a Device CAL (one machine, any user) — most offices default to User CALs unless staff share workstations across shifts. CALs are cumulative: a 15-person office running Standard Edition needs 1 server license plus 15 CALs, whether bought individually or in a bundle like a 24-CAL or 100-CAL pack.
The External Connector Exception
Server + CAL is built around a known, internal population, not public-facing access. If external users (customers, partners, the public) need to reach the database, Microsoft requires switching to Per-Core licensing or adding an External Connector license rather than buying CALs per outside user — impractical to track and expensive to true up.
Which Model Is Cheaper? Finding the Breakeven Point
There’s no single number that fits every deployment — list prices vary by SQL Server version, edition, and reseller — but the logic behind the decision is consistent.
Server + CAL tends to win when user count is small and stable: for a handful of people, one server license plus a small stack of CALs usually beats the price of a minimum 4-core Per-Core deployment. As headcount grows, though, each added CAL keeps raising the bill while the Per-Core price stays flat once hardware is licensed — so there’s a crossover point, specific to your core count and current pricing, beyond which Per-Core wins. Rather than chasing a fixed cutoff, model both totals for your actual hardware and headcount: minimum cores × per-core price, versus one server license plus a CAL per real user. Whichever total is lower — and whichever fits your access pattern — is your answer.
Growth trajectory matters too. A 12-person team expecting to double within a year may be better off licensing Per-Core now rather than repeatedly re-buying CALs.
Standard vs Enterprise Edition Licensing Differences
The licensing model is only half the decision — the edition you pick constrains which models are even available.
Standard Edition supports both models: Per-Core or Server + CAL, whichever fits your user count and access pattern. It covers core relational database features and a practical performance ceiling for small-to-midsize workloads.
Enterprise Edition is licensed Per-Core only — there is no Server + CAL option. If you need Enterprise-only capabilities (advanced high availability, larger scale limits, advanced analytics), Per-Core isn’t a choice you weigh, it’s the required path, regardless of headcount.
Also weighing the OS layer underneath SQL Server? Our guide to Windows Server 2016 vs 2019 vs 2022 vs 2025 covers how OS edition choices interact with this math.
Virtualization Considerations
Most SQL Server deployments today run on VMs rather than bare metal, which changes the licensing arithmetic slightly.
Under Per-Core, you can license either the physical host (covering every VM on it, up to the licensed core count) or license individual VMs by their assigned virtual cores, subject to the same 4-core minimum. Enterprise Edition with Software Assurance unlocks unlimited virtualization — any number of SQL Server VMs on a fully-licensed host at no extra per-VM cost, a major reason dynamic environments lean Enterprise + Per-Core.
Under Server + CAL, virtualization doesn’t reduce license count the same way — each VM instance still needs its own server license, and CAL count is still driven by total unique users, not VM count. For the broader infrastructure cost picture, see our breakdown of Windows Server vs Linux total cost of ownership.
Buyer’s Guide
Choose Per-Core if:
- Your database sits behind a customer-facing website, e-commerce store, or SaaS app with an unknown or growing number of end users.
- You run (or plan to run) SQL Server Enterprise Edition — Per-Core is your only option.
- You’re heavily virtualized and want unlimited VMs on a licensed host.
- Tracking exact named users is impractical, or your count exceeds the rough breakeven point for your hardware.
Choose Server + CAL if:
- You have a small office with a known, stable team — e.g., 15 accounting or operations staff connecting to one internal Standard Edition instance.
- Your database is purely internal, with no public-facing or anonymous access requirement.
- Your user count is comfortably below the crossover point and you don’t expect fast headcount growth.
Who should avoid overbuying: a small business with 10 known employees querying an internal reporting database has no reason to buy a 4-core-minimum Per-Core license — that’s paying for capacity nobody uses. Conversely, a growing SaaS company putting a customer-facing database behind Server + CAL risks a compliance gap or a runaway CAL bill as the user base scales — that workload belongs on Per-Core from day one.
Why This Matters for You
SQL Server licensing mistakes are expensive in both directions. Under-licensing — too few core licenses, or serving external users without the right CAL structure — creates real compliance exposure in an audit. Over-licensing wastes budget on capacity or seats you’ll never use. Matching the model to how your database is actually accessed, with headroom for where you’re headed, also affects which edition you can consider, since Enterprise features come locked to Per-Core pricing. Getting this right once avoids a costly re-licensing exercise later — see our guide on how software license resale works for background on buying genuine Microsoft licenses through a reseller.
Frequently Asked Questions
What does “SQL Server licensing per core vs CAL” actually mean?
It refers to the two ways Microsoft lets you license SQL Server: Per-Core, where you pay based on physical processor cores and get unlimited user access, or Server + CAL, where you pay a base server license plus a Client Access License for every named user or device that connects.
Can I mix Per-Core and Server + CAL on the same server?
No. Each SQL Server instance must be licensed entirely under one model — not part Per-Core, part CAL, on the same instance.
Is Server + CAL available for SQL Server Enterprise Edition?
No. Enterprise Edition is licensed Per-Core only, regardless of how few users you have.
How many core licenses do I need for a single 6-core processor?
You need at least 4 core licenses per physical processor, or the actual core count if higher, purchased in packs of two. A 6-core processor needs 6 core licenses, not 4.
Do I need a CAL for every device, or just every user?
One or the other, not both, per person or machine. A User CAL covers one person across any device; a Device CAL covers one device regardless of who’s using it. User CALs are usually simpler for standard office setups.
Does Per-Core licensing cover users outside my company?
Yes. Per-Core permits an unlimited number of internal or external/anonymous users and devices to connect — a key reason it fits customer-facing applications.
What happens if I use Server + CAL but customers access the database through a public website?
That doesn’t fit Server + CAL, which is built for known internal users. Public or anonymous access requires switching to Per-Core licensing or adding an External Connector license.
Is Per-Core always more expensive than Server + CAL?
Not necessarily. For small, fixed teams, Server + CAL is often cheaper; as user count grows, Per-Core’s flat hardware-based cost tends to win out.
How does virtualization change which model I should pick?
Heavily virtualized environments often favor Per-Core, especially Enterprise Edition with Software Assurance, which allows unlimited SQL Server VMs on a fully-licensed host. Server + CAL still requires a server license per VM instance.
Which SQL Server edition should a small business with 15 known users choose?
Standard Edition with Server + CAL licensing (1 server license plus 15 CALs) typically fits this scenario, assuming Standard covers your feature needs and all 15 users are internal, named staff.
Conclusion
Weighing SQL Server licensing per core vs CAL comes down to one question: is your user base small, known, and internal, or large, unpredictable, and possibly public-facing? Server + CAL keeps costs low for the former; Per-Core is the only option for the latter, and it’s mandatory for Enterprise Edition. Model both totals against your actual core count and headcount, factor in growth and virtualization plans, then pick the edition that supports the model you need. Once decided, see our MAK vs KMS activation guide, or compare against Exchange Server 2019 vs Microsoft 365 if weighing other server-side Microsoft products.
Ready to license your deployment? Browse genuine, instantly-delivered SQL Server keys for both models:
Per-Core options:
- SQL Server 2019 Standard Edition Product Key
- SQL Server 2019 Enterprise License Product Key
- SQL Server 2017 Standard Edition License Key (10 and 24 Cores)
- SQL Server 2016 Standard Cores License Key
Server + CAL options:
- SQL Server 2022 Standard 1 User CAL License Key
- SQL Server 2022 Standard 100 User CAL License Key
- SQL Server 2019 Standard Edition 24 CALs Product Key
- SQL Server 2016 Standard 50 Users Product Key
You can also browse the full SQL Server license catalog to compare every version side by side.
Trust & Support
Every license comes with a 30-day money-back guarantee, instant digital delivery, and 24/7 support. Questions before or after you buy? Email contact@softlicensedeals.com or message us on WhatsApp at +1 (323) 218-6077. You can also check our FAQ or browse our Installation Guides for step-by-step activation help.
