SQL Server can be licensed in two ways: per core, or per server with Client Access Licences (Server + CAL). The right model depends on how many people or devices use the database and whether you can count them. This guide explains both models, the rules that catch people out, and how to work out which is cheaper for you.
The two models at a glance
| Per Core | Server + CAL | |
|---|---|---|
| Available for | Enterprise and Standard | Standard only |
| What you license | Every core the instance can use | Each server, plus each user or device |
| Users and devices | Unlimited | One CAL each |
| Internet-facing or uncountable users | Allowed | Not practical |
Per Core licensing
- Core licences are sold in packs of two.
- On a physical server you license all physical cores, with a minimum of four core licences per physical processor.
- In a virtual machine you license the virtual cores assigned to it, with a minimum of four core licences per VM.
- No CALs are needed, however many users or applications connect.
Per Core is the only option for Enterprise edition, and the only sensible one for public websites, customer portals and any workload where you cannot count who connects.
Server + CAL licensing
- You buy one server licence for each server or VM running SQL Server Standard.
- Every user or device that accesses the data needs a SQL Server CAL. A User CAL covers one person on any device; a Device CAL covers one device for any number of people.
- The CAL version must be the same as, or newer than, the SQL Server version it accesses. One CAL can access any number of licensed servers.
Multiplexing does not reduce CALs
If users reach the database through a web application, an ERP system or a reporting tool that uses a single service account, each of those users still needs a CAL. Microsoft counts the people and devices at the front end, not the connections at the back end. This is the most common cause of an under-licensed installation.
How to work out which is cheaper
- Count the users or devices that will touch the data, directly or through an application.
- Add up the Server + CAL cost: one server licence plus one CAL for each of them.
- Add up the Per Core cost: the number of cores (at least four) divided by two, multiplied by the price of a two-core pack.
- Compare the totals, then repeat with the user count you expect in three years.
For a small internal system with a few dozen named users, Server + CAL is normally cheaper. As the user count grows, or once the server is exposed to external users, Per Core wins.
Standard edition limits
Whichever model you choose, Standard edition caps what a single instance can use. In SQL Server 2022 the limit is the lesser of 4 sockets or 24 cores, and 128 GB of buffer pool memory. SQL Server 2025 raises this to 32 cores and 256 GB. If you need more, you need Enterprise, which is Per Core only.
Virtualization and failover
- From SQL Server 2022 onward, licensing individual virtual machines requires Software Assurance or subscription licences.
- Passive failover replicas are covered without extra licences only with Software Assurance.
- Developer edition is free for development and testing, and Express is free for small production databases up to 10 GB.
Related: SQL Server 2022 Standard and SQL Server 2025 Standard. SQL Server runs on Windows Server, which has its own access licences; see our Windows Server CAL guide.




