Fix it now
Both products count physical cores and round upwards, but the floors are different and that is where under-buying happens. Windows Server needs a minimum of 8 core licences per physical processor and 16 per server. SQL Server needs a minimum of 4 core licences per physical processor. Windows Server sells in 2-packs and 16-packs; SQL Server in 2-packs only.
- Count every physical core in the server, then apply both Windows Server floors and take whichever produces the larger number.
- Count every physical core for SQL Server too, applying the 4-per-processor floor. There is no separate per-server floor on SQL Server.
- Use the virtual-machine models only where you hold Software Assurance or subscription licences: minimum 8 core licences per VM and 16 per customer for Windows Server, minimum 4 per virtual OSE for SQL Server.
- Ignore hyper-threading when licensing physical cores. When licensing virtually, a virtual core maps to a hardware thread.
- Add Windows Server CALs to every quote. Core licences cover the server; they do not cover anyone connecting to it.
- Compare Datacenter before you buy a third set of Standard core licences for the same server. Standard gives two operating system environments per complete set.
System Center follows the Windows Server pattern: 8 core licences per processor and 16 per server, sold in 2-packs, with a minimum of 8 per virtual machine and 16 per customer.
If you have the processor and core layout in front of you, the arithmetic below settles the order. Below is a worked table for common configurations, the virtual-machine rules, and the mistakes that survive into purchase orders.
Why it happens
Core licensing looks simple until you meet the floors, and the floors are what people get wrong. Microsoft’s core-based licensing guidance sets Windows Server at a minimum of eight core licences per physical processor and sixteen per server, with SKUs sold in 2-pack and 16-pack sizes. SQL Server and BizTalk Server sit at a minimum of four core licences per physical processor, with SKUs sold in packs of two core licences each. Applying the rule you remember from one product to the other is the single most common cause of an under-bought order.
Both floors apply at once on Windows Server, and you take whichever is larger. A single-processor four-core server needs sixteen core licences because of the per-server floor. A two-processor server with six cores each has twelve physical cores, needs eight per processor and sixteen per server, and therefore needs sixteen. A two-processor server with ten cores each has twenty physical cores, clears both floors, and needs twenty. The rule is: count the physical cores, then raise the answer to whichever floor is higher.
SQL Server behaves differently in a way that matters when you specify hardware. It has a per-processor floor of four and no separate per-server floor, so a single-processor four-core box needs four SQL core licences while needing sixteen Windows Server ones. That asymmetry is why a server sized for Windows Server minimums and a server sized for SQL Server economics are not the same server, and why the two conversations should happen together rather than in sequence.
You are choosing between two small processors and one larger one
You have this one if A specification decision with the same total core count available either way.
- Add up the per-processor floors before you decide. Two six-core processors trigger a sixteen-licence Windows Server bill for twelve physical cores; one twelve-core processor triggers the same sixteen because of the per-server floor.
- On SQL Server the difference is real: two four-core processors need eight core licences, one eight-core processor needs eight as well, but two eight-core processors need sixteen where one sixteen-core processor also needs sixteen. Run the sum rather than assuming.
- Where SQL Server is the expensive licence on the box, fewer sockets with more cores each is usually the cheaper specification.
You are licensing a single virtual machine rather than the host
You have this one if One SQL Server or one Windows Server guest on a large, densely shared host.
- Both products allow it, and both restrict it to customers with subscription licences or active Software Assurance.
- SQL Server: licence the virtual cores assigned to the virtual OSE, with a minimum of four core licences per virtual OSE, sold in 2-packs.
- Windows Server: minimum eight core licences per virtual machine and sixteen per customer.
- When licensing virtually, a virtual core maps to a hardware thread – so hyper-threading does change the count in the virtual model even though it does not in the physical one.
The guest count is climbing on a Standard host
You have this one if A third or fourth Windows virtual machine going onto a host already licensed once with Standard.
- Standard permits two operating system environments per fully licensed server. For each further pair, the server must be relicensed for the same number of core licences.
- Divide the Datacenter figure on your quote by the Standard figure for the same cores and round up. That is how many two-machine Standard sets one Datacenter set is worth.
- The core count does not move that crossover – it appears on both sides of the sum and cancels. Only the price ratio you are quoted moves it.
The quote has no CALs on it
You have this one if A Windows Server order priced entirely in core licences.
- Windows Server core licences cover the server software. Every user or device accessing it needs a Windows Server CAL, with External Connector licences as the alternative for external users.
- Remote Desktop Services and Active Directory Rights Management Services need additive access licences on top of the base CAL.
- Buy CALs at the version of your newest server: a user CAL allows access to the corresponding version of the server software or earlier versions.
Full reference
The minimums, product by product
| Rule | Windows Server | SQL Server | System Center |
|---|---|---|---|
| What you count | All physical cores on the server | All physical cores on the server | All physical cores on the server |
| Minimum per physical processor | 8 core licences | 4 core licences | 8 core licences |
| Minimum per server | 16 core licences | None separately published | 16 core licences |
| Minimum per virtual machine | 8 core licences, and 16 per customer | 4 core licences per virtual OSE | 8 per VM, 16 per customer |
| Virtual-machine model requires | Software Assurance or subscription licences | Software Assurance or subscription licences | Software Assurance or subscription licences |
| Pack sizes | 2-packs and 16-packs | 2-core packs | 2-packs |
| Hyper-threading, physical licensing | Count physical cores | Does not change the count | Count physical cores |
| Hyper-threading, virtual licensing | A virtual core maps to a hardware thread | A virtual core maps to a hardware thread | A virtual core maps to a hardware thread |
| Client Access Licences | Required per user or device | Not required under per core; required under Server plus CAL | Not applicable |
| Alternative model | None; core licensing only | Server plus CAL, on Standard edition | Management server licensing |
Worked examples
| Server | Physical cores | Windows Server core licences | SQL Server core licences |
|---|---|---|---|
| 1 processor, 4 cores | 4 | 16, forced by the per-server floor | 4, forced by the per-processor floor |
| 1 processor, 8 cores | 8 | 16, forced by the per-server floor | 8 |
| 1 processor, 12 cores | 12 | 16, forced by the per-server floor | 12 |
| 2 processors, 6 cores each | 12 | 16, forced by both floors | 12 |
| 2 processors, 10 cores each | 20 | 20 | 20 |
| 2 processors, 16 cores each | 32 | 32 | 32 |
| 4 processors, 10 cores each | 40 | 40 | 40 |
Read the first row as the general warning. Buying deliberately small hardware to reduce a Windows Server bill does not work: the sixteen-core floor is the entry price whatever is fitted. Specify the processor on its technical merits, and treat sixteen core licences as the minimum Windows Server line on any quote.
Which model to licence a virtual estate under
There are two ways to licence a virtualised workload and the cheaper one depends entirely on density. Licensing the host covers every physical core on the server and then grants operating system environments according to edition: two on Windows Server Standard, any number on Datacenter, and for SQL Server, unlimited instances in unlimited operating system environments where Enterprise is licensed with Software Assurance or subscription licences. Licensing individual virtual machines instead counts the virtual cores assigned, subject to the minimums, and requires Software Assurance or subscription licences.
On a large host running a couple of small guests, the per-virtual-machine model usually wins – licensing sixty-four physical cores to run two four-core virtual machines is rarely the cheaper arithmetic. On a densely packed host the physical model wins comfortably. Work out both and take the smaller number; there is no rule of thumb that survives contact with an actual hardware specification.
Failover, which is where SQL Server people lose money
SQL Server passive failover rights are a Software Assurance and subscription benefit, and they are worth more than most people realise. For each operating system environment licensed with Software Assurance or subscription licences, you may run one passive failover replica for high availability and one for disaster recovery in separate operating system environments, plus one in Azure. Without that coverage every replica has to be licensed as though it were active, which frequently doubles or triples the bill on a design that was supposed to be resilient rather than expensive.
The same principle applies on Windows Server clusters from a different angle. Licences are assigned to a physical server and cannot be reassigned between server farms within 90 days of the last assignment, so every node a workload might land on has to be licensed for the worst case it could carry. That is why cluster costing has to start from what each node might have to run, not from what it runs today.
The mistakes that reach a purchase order
- Applying the SQL Server four-core floor to Windows Server, which under-buys by eight or twelve licences on small hardware.
- Counting logical processors instead of physical cores when licensing a physical server. Hyper-threading does not change the physical count.
- Buying core licences for the host and forgetting Windows Server CALs entirely, then discovering they are the larger number.
- Assuming Standard’s two operating system environments is a per-server allowance you can grow past. It is a per-complete-set allowance.
- Buying CALs at the version of the oldest server rather than the newest. A user CAL reaches the corresponding version or earlier, never later.
- Costing a cluster on today’s placement rather than the worst case each node might carry after a failover.
When a licence is the actual fix
The most expensive mistake in this part of the range is ordering core licences to match a core count without applying the floors, and finding the shortfall at audit rather than at purchase. Windows Server 2025 Standard core licences are sold in 2-packs and 16-packs, and Arco will check your processor and core configuration against both the eight-per-processor and sixteen-per-server minimums before the order goes in, along with the User or Device CAL count you will need alongside them. If your virtualisation plans make Datacenter cheaper than relicensing the same cores repeatedly, we will say so rather than sell you the same Standard set three times – and if a single SQL Server guest on a large host is better licensed per virtual machine, we will price that comparison too.
Questions people ask about this
Why does a four-core server need sixteen Windows Server core licences?
Because the minimums are eight core licences per physical processor and sixteen per server, and you take whichever produces the larger number. Sixteen is the entry price for Windows Server on any physical machine, which is why buying deliberately small hardware saves nothing on licensing.
Does SQL Server have a sixteen-core floor too?
No, and this is the difference that catches people. SQL Server’s published minimum is four core licences per physical processor, with no separate per-server floor. A single-processor four-core box therefore needs four SQL Server core licences and sixteen Windows Server ones.
Does hyper-threading change the count?
Not when you licence physical cores – Microsoft states the use of hyper-threading does not affect the number of core licences required in physical environments. It does matter in the virtual model, where a virtual core maps to a hardware thread, so a virtual machine assigned eight virtual processors on a hyper-threaded host is counted as eight.
Can I licence just the virtual machine instead of the whole host?
Yes, but only with subscription licences or active Software Assurance, and the floors still apply: eight core licences per virtual machine and sixteen per customer for Windows Server, and four core licences per virtual operating system environment for SQL Server. On a large host running a couple of small guests it is usually the cheaper model; on a dense host it is not.
How are the licences sold?
Windows Server core licences come in 2-packs and 16-packs. SQL Server and BizTalk Server core SKUs are sold in packs of two core licences each, as is System Center. You cannot buy an odd number of core licences in any of them.
Do core licences cover the people connecting to the server?
No. Windows Server core licences cover the server software only; every user or device that accesses it needs a Windows Server CAL, or an External Connector licence for external users. Remote Desktop Services and Active Directory Rights Management Services need additive access licences on top of the base CAL. SQL Server licensed per core needs no CALs at all, which is one of the reasons per-core is used for public-facing databases.
