Windows Server and SQL Server core licensing, with the invoice math

The three rules

Every awkward server licensing question resolves to these.

• Rule 1 — licence all physical cores in the host, not the cores you assigned to VMs
• Rule 2 — respect the minimums: 8 cores per processor, 16 per server, and for SQL 4 cores per VM
• Rule 3 — cores are sold in 2-core packs, so always round up to an even number

Worked example: a 2×8-core host

A dual-socket host with eight cores per socket has 16 physical cores. That is exactly the server minimum, so you buy 16 core licences (eight 2-core packs) of Windows Server Standard. Standard then permits two virtual instances on that host.

Need four VMs on the same box? Either stack a second full 16-core set of Standard licences, or move to Datacenter and stop counting. The crossover in practice arrives at around 12–14 VMs per host.

SQL Server: where the 4-core VM minimum bites

Licensing SQL Server 2022 Standard on a 2-vCPU VM still costs four core licences because of the per-VM minimum. Two such VMs cost eight core licences — often more than licensing the small physical host outright.

SQL Server Express remains free but caps the database at 10 GB, 1 GB of buffer pool and a single socket or four cores. Growth past any one of those caps forces the Standard purchase.

• Per-core licensing needs no CALs and permits unlimited users
• Server+CAL licensing can be far cheaper for small, known user counts
• Container and CI workloads still consume core licences on the underlying host

CALs: the line item people forget

Windows Server core licences cover the server operating system, not the right for people to use it. Every user or device that connects needs a CAL. Choose user CALs when staff use several devices, device CALs when several staff share a machine such as a shop till or shift terminal.

Remote Desktop is a separate CAL again — a common gap in audits.