SQL Server 2022 Licensing Explained: Per Core vs Server + CAL, and Standard vs Enterprise
Buying SQL Server 2022 comes down to two decisions:
- Which edition: Standard or Enterprise.
- Which licensing model: Per Core, or Server + CAL (client access licenses).
This guide explains both in plain English, based on Microsoft’s SQL Server 2022 licensing guide, datasheet, and edition documentation. It ends with worked examples so you can count what you need.
The quick answer
- Enterprise is licensed per core only.
- Standard can be licensed per core or with Server + CAL.
- Per Core covers unlimited users and devices with no CALs. You license the processor cores.
- Server + CAL means one server license for each operating system environment running SQL Server, plus one CAL for each user or device that accesses it.
- Server + CAL usually suits a business with a known, countable group of internal users. Per Core suits public-facing or hard-to-count workloads, and it’s the only option for Enterprise.
The SQL Server 2022 editions
Microsoft offers two main commercial editions and two free ones:
- Enterprise: Microsoft’s premier edition, for mission-critical workloads that need the highest performance, scale, and availability.
- Standard: fully featured database capabilities for mid-tier applications and data marts. This is the edition most small and mid-sized businesses use.
- Developer (free): has all the features of Enterprise, but is licensed for development and test only, not production.
- Express (free): an entry-level edition for learning and small applications. Microsoft limits it to the lesser of 1 socket or 4 cores, and 10 GB per database.
Microsoft also has a Web edition, which it offers only to hosting providers through the Services Provider License Agreement (SPLA).
Licensing model 1: Per Core
With Per Core licensing, you license the processor cores of the server that runs SQL Server. Microsoft’s rules for a physical server:
- License every physical core in the server.
- At least 4 core licenses per physical processor, even if the processor has fewer cores.
- Core licenses are sold in 2-core packs, so divide the number of cores you need by two to get the number of packs.
- No CALs are needed. Microsoft says Per Core allows an unlimited number of users or devices to connect, from inside or outside your organization’s firewall.
- Hyper-threading doesn’t change the count on a physical server. You count physical cores.
Microsoft says Per Core is the right model when:
- You’re deploying Enterprise edition.
- The workload is internet- or extranet-facing, or connects to external-facing systems.
- You can’t easily count the users or devices.
- Per Core simply works out cheaper than Server + CAL for your Standard deployment.
Licensing model 2: Server + CAL (Standard only)
Server + CAL is available for Standard edition only. Microsoft’s rules:
- Each operating system environment (OSE) running SQL Server needs a SQL Server server license. An OSE is a physical server’s operating system or a single virtual machine.
- One server license lets you run any number of SQL Server instances in that one OSE.
- Every user or device that accesses SQL Server needs a SQL Server CAL. You choose user CALs, device CALs, or a mix.
- CALs must be the same version as the server or newer. Microsoft’s example: to access a SQL Server 2019 Standard server, a user needs a 2019 or 2022 CAL.
- One CAL covers access to multiple licensed SQL Servers, so a user with one SQL Server 2022 CAL can reach every licensed SQL Server 2022 (or earlier) server you run.
- Devices that aren’t operated by people, such as sensors or automated equipment, need device CALs, even when they connect indirectly.
- Multiplexing doesn’t reduce CALs. If people reach SQL Server through an app, a web front end, or other pooling software, you still count the people or devices at the front end.
User CAL or device CAL? A user CAL covers one person on any device. A device CAL covers one device used by any number of people. Most offices where each person has a laptop and a phone choose user CALs. Shift-based teams sharing a few PCs often choose device CALs.
Note that SQL Server CALs are separate from Windows Server CALs. If your SQL Server runs on Windows Server, the people or devices that access it generally need Windows Server CALs too. See our guide to Windows Server User vs Device CALs.
Per Core vs Server + CAL at a glance
| Per Core | Server + CAL | |
|---|---|---|
| Editions | Enterprise and Standard | Standard only |
| What you license | Every physical core (min. 4 per processor) | One server license per OSE |
| User or device licenses | None needed | One CAL per user or device |
| External or public users | Covered | Each needs a CAL |
| Sold as | 2-core packs | Server license + individual CALs |
| Best for | Web-facing or hard-to-count workloads, Enterprise | A known number of internal users |
Licensing SQL Server in virtual machines
Virtual machines are where SQL Server licensing gets tricky. Microsoft’s rules differ by model.
Server + CAL in VMs: buy one server license per VM running SQL Server, regardless of how many virtual processors the VM has. Microsoft’s example: six VMs running Standard need six Standard server licenses. Microsoft says this doesn’t require Software Assurance or a subscription. You still need CALs for the users or devices.
Per Core in VMs: license the virtual cores in each VM, with at least 4 core licenses per VM. Microsoft says licensing individual VMs by core requires subscription licenses or licenses with active Software Assurance. For Standard edition under Per Core, Microsoft says licensing individual VMs is the only option in a virtualized environment.
Enterprise for many VMs: if you license every physical core of a host with Enterprise core licenses, Microsoft lets you run SQL Server in a number of VMs equal to the number of core licenses assigned. With Software Assurance, Enterprise adds unlimited virtualization on that host.
If you’re licensing SQL Server in VMs, request a quote and tell us how many VMs and virtual cores you have. We’ll help you choose the right license type.
Standard vs Enterprise: what’s the difference?
Scale limits
| Limit (per instance) | Standard 2022 | Enterprise 2022 |
|---|---|---|
| Compute | Lesser of 4 sockets or 24 cores | Operating system maximum |
| Buffer pool memory | 128 GB | Operating system maximum |
| Columnstore segment cache | 32 GB | Unlimited |
| Memory-optimized data per database | 32 GB | Unlimited |
| Maximum database size | 524 PB | 524 PB |
High availability
- Standard includes basic availability groups (two replicas, one database per group) and Always On failover cluster instances with two nodes. It also includes log shipping, backup compression, and accelerated database recovery.
- Enterprise adds full Always On availability groups with up to 8 secondary replicas, plus contained and distributed availability groups, failover cluster instances with up to 16 nodes, online index create and rebuild, and online page and file restore.
Performance and management
Enterprise-only features in Microsoft’s list include Resource Governor, batch mode on rowstore and other intelligent query processing features such as automatic tuning, NUMA-aware large page memory, and parallel consistency checks. Replication options such as peer-to-peer transactional replication and Oracle publishing are also Enterprise only.
Security is mostly the same
Good news for Standard buyers: Microsoft lists Transparent Data Encryption (TDE), Always Encrypted, row-level security, dynamic data masking, ledger, encrypted backups, and server and database audit in both Standard and Enterprise.
Which edition should you choose?
Choose Standard if:
- Your instance fits within 24 cores and 128 GB of buffer pool memory.
- Basic availability groups or a two-node failover cluster meet your uptime needs.
- You want the option of Server + CAL licensing for a known group of users.
Choose Enterprise if:
- You need more than Standard’s compute or memory limits.
- You need full Always On availability groups with readable secondaries, more replicas, or online index operations.
- You plan to run SQL Server in many VMs on one host and want to license the host once.
Worked examples
These examples count licenses only. Pricing depends on your quote.
1. Small office, one physical server, 25 staff. The server has one 8-core processor and runs SQL Server 2022 Standard for an internal accounting app. All 25 staff use it.
- Server + CAL: 1 Standard server license + 25 SQL Server 2022 user CALs.
- Per Core: 8 core licenses (four 2-core packs). No CALs.
- Compare both quotes. With a small, fixed team, Server + CAL is often the one to check first.
2. Customer-facing website. The database behind a public online store is accessed by people you can’t count. Use Per Core. Customers would each need a CAL under Server + CAL.
3. Small processors. A server has two processors with 2 cores each (4 physical cores in total). Because Microsoft requires at least 4 core licenses per processor, Per Core needs 8 core licenses, not 4.
4. Three VMs on one host. Each VM runs SQL Server Standard for internal users. Under Server + CAL, that’s 3 server licenses plus CALs for the users or devices. Under Per Core, you’d license each VM’s virtual cores (minimum 4 per VM), which requires a subscription or Software Assurance.
How to buy
- For Server + CAL, see our SQL Server 2022 Standard server license and SQL Server 2022 User CALs, or browse all SQL Server licenses. For Per Core licensing, request a quote.
- For Enterprise edition, Per Core licensing, or VM setups, request a quote. Tell us the edition, how many servers or VMs, the core count of each, and how many users or devices need access. We’ll put together the right mix of licenses.
After you order, follow the installation and activation steps included with your order. If anything doesn’t work as expected, contact our support team and we’ll help you sort it out.
Frequently asked questions
With Per Core licensing, you license every physical core of the server (at least 4 per processor), and any number of users or devices can connect with no CALs. With Server + CAL, you buy one server license for each operating system environment running SQL Server, plus a CAL for each user or device that accesses it. Server + CAL is available for Standard edition only.
No. Microsoft licenses SQL Server 2022 Enterprise per core only. Microsoft’s Product Terms say new Enterprise Server/CAL licenses are no longer available.
On a physical server, you need one core license for every physical core, with a minimum of 4 core licenses per physical processor. Core licenses are sold in 2-core packs. In a virtual machine licensed by core, you license the virtual cores, with a minimum of 4 per VM, and Microsoft requires a subscription or Software Assurance for that option.
No. Microsoft says the Per Core model allows unlimited users or devices to connect, from inside or outside your firewall, without CALs.
Yes. Microsoft says CALs must be the same version as the server or newer. A SQL Server 2022 CAL can access SQL Server 2022 and earlier versions. A SQL Server 2019 Standard server can be accessed with a 2019 or 2022 CAL.
Microsoft limits a SQL Server 2022 Standard instance to the lesser of 4 sockets or 24 cores, and 128 GB of buffer pool memory. Standard supports basic availability groups and two-node failover cluster instances. Enterprise uses the operating system maximum for compute and memory.
No. Microsoft says SQL Server Developer edition includes all Enterprise features but is licensed for development, test, and demonstration only, not production use.
Questions about SQL Server licensing?
Not sure which model or edition fits, or licensing several servers or VMs? We’re happy to help.
- Business or volume orders: request a quote.
- Help with an order: email support@solveditservices.com (fastest), or call (447) 223-5297.
- More answers are on our FAQ page.