SQL Server 2022 Licensing: Core vs CAL Explained
SQL Server 2022 licensing trips up a lot of teams because Microsoft sells it two different ways: per-core and Server+CAL. Pick the wrong model and you either overpay or fall out of compliance. This guide walks through both models, the minimums, virtualization and container rules, and how runtime licensing fits in.
Core-based licensing: the default for public workloads
Under the core model you license every physical core on the host that runs SQL Server, with a minimum of 4 cores per physical processor and 4 cores per server. In a virtual machine you license at least 4 virtual cores per VM. Software Assurance adds License Mobility so you can move licenses between servers instead of buying new ones. If the database is reachable from the internet - a website backend, an API, a SaaS product - core licensing is effectively mandatory because you cannot count anonymous internet users.
Server + CAL: cheaper for internal teams
The Server+CAL model licenses the server once, then requires a Client Access License for each named user or each device that touches the database. There is no user minimum, but the server itself must have at most 20 cores before Software Assurance core factors apply, which caps how far you can scale this model. A 40-person company running one internal ERP database is the textbook case: one Standard server license plus 40 user CALs costs far less than licensing 16 cores.
Standard or Enterprise: what you actually get
Standard Edition caps the database engine at the smaller of 4 sockets or 24 cores and limits buffer pool size to 128 GB per instance. Enterprise removes those caps and adds unlimited virtualization with Software Assurance, advanced availability features like distributed availability groups, and full online operations. For most line-of-business databases Standard is enough; Enterprise earns its price on consolidation hosts, always-on replication at scale, or compliance workloads that need the extra features.
Virtualization rules in plain language
Without Software Assurance you license the virtual cores of each VM individually, with the same 4-core minimum. With Software Assurance you can buy Enterprise cores for the physical host once and run unlimited VMs on that host - the License Mobility benefit that makes Enterprise the consolidation choice. Containers follow the same logic: you license the cores available to the container runtime, again with the 4-core floor, and containers on a properly licensed host inherit its coverage.
Runtime and embedded scenarios
ISVs and appliance builders often need SQL Server embedded in a product they sell. Runtime licensing through the SQL Server Runtime Function License lets the ISV bundle SQL Server under their own terms, with the license counted against the cores the runtime can address. If you ship a physical or virtual appliance with SQL inside, ask your licensing contact for the runtime agreement rather than reselling boxed licenses - the terms and support model are different.
The compliance traps to avoid
Three mistakes dominate audits: running a passive failover replica without failover rights (Software Assurance includes one passive failover per licensed active server, but the passive server cannot serve user requests); buying CALs for admin and service accounts that never connect directly; and upgrading cores on a host without re-counting licenses. Keep an inventory of hosts, cores and CALs in one spreadsheet and reconcile it quarterly - it turns a stressful audit into a ten-minute check.
Buying genuine SQL Server licenses
Genuine SQL Server 2022 keys activate against Microsoft servers, receive security updates, and can be verified by any auditor. KeyStarter supplies SQL Server 2022 and 2019 runtime licenses with instant delivery and support, plus the Windows Server licenses that sit underneath them. If you are unsure which model fits your workload, send us your user count and core layout and we will price both paths so you can compare.
At a glance
| Model | How it is counted | Best for |
|---|---|---|
| Core-based | Every physical core on the server (or every virtual core per VM), 4-core minimum | Public-facing apps, unlimited users, virtualization-heavy estates |
| Server + CAL | One server license plus a CAL for every user or device | Internal apps with a known, limited user count |
| Runtime (containers/IoT) | Licenses follow the cores the container runtime can use | Containerized and embedded SQL workloads |
Buy SQL Svr Std RUNTIME 2022 - Volume LicenseBuy SQL Svr Std RUNTIME 2019 IoT 1 Clt - Volume Licensing
Frequently asked questions
Do I need a CAL for the SQL Server administrator?
No. Administrators managing the server (including service accounts) do not consume a CAL. CALs are only for users or devices that access the database data through your application.
What is the minimum core count for SQL Server 2022?
Four cores per physical processor or per VM, and at least four cores total per server, regardless of how small the workload is.
Can I switch from Server+CAL to Core licensing later?
Yes, by buying core licenses with Software Assurance and using the step-up path, but you cannot switch back. Price both models before you commit if your user count might grow.