Windows Server 2012 updates ended on 13 October 2026. Windows Server 2016 support ends in January 2027. Is your estate ready?
Get Windows Server and SQL Server licensing right, including Hyper-V. Core minimums, edition choices, hypervisor rules and end-of-support deadlines all change what you owe. Rythium combines proprietary telemetry analytics with deep server licensing expertise to help enterprise IT leaders right-size their estate, use the rights they already own, and enter audits and renewals with verified data.
5–20%Typical reduction in server license requirement, based on Rythium engagements
| Product | Per | List |
|---|---|---|
| Windows Server Standard | 16 cores | $1,176 |
| Windows Server Datacenter | 16 cores | $6,771 |
| SQL Server Standard | 2 cores | $3,945 |
| SQL Server Enterprise | 2 cores | $15,123 |
Volume agreements, CSP and subscription pricing differ.
Windows Server and SQL Server are licensed by cores, editions, virtual machines and rights that depend on whether you hold Software Assurance. Small mistakes in any of these multiply across hosts and clusters. The six most common traps:
Core-counting errorsWindows Server needs at least 8 core licenses per processor and 16 per server, so a small server can require more licenses than it has cores. SQL Server has its own minimum: 4 core licenses per processor and per virtual machine.
Edition mismatchSQL Server Enterprise is priced at roughly four times Standard per core. Where Standard meets the workload’s needs, the gap is large (see the worked examples below).
Virtualization mismatchChoosing Windows Server Standard where Datacenter is cheaper, or the reverse, and licensing SQL Server per VM where host-level licensing would cost less.
Hypervisor blind spotsLicensing every host a VM can move to, host roles that use up virtualization rights, and platform changes such as leaving VMware all affect what you owe.
Unused Software Assurance rightsPassive failover and disaster recovery rights, Azure Hybrid Benefit and per-VM licensing options that go unclaimed.
Out-of-support serversSQL Server 2016 and Windows Server 2012 are already past their dates, and Windows Server 2016 follows in January 2027. Extended Security Updates cost money and are not a long-term plan.
A quick reference. Always confirm against Microsoft’s Product Terms for your agreement and version.
| Rule | Windows Server 2025 | SQL Server 2025 |
|---|---|---|
| Licensing metric | Per physical core (Standard and Datacenter), plus CALs for users or devices | Per core (Standard and Enterprise), or Server + CAL for Standard |
| Minimum cores | 8 core licenses per processor and 16 per server | 4 core licenses per physical processor, and 4 per VM when licensing by VM |
| Pack sizes | 2-core and 16-core packs | 2-core packs |
| Virtualization rights | Standard: 2 OSEs per license set (stack for more). Datacenter: unlimited | Enterprise with active SA: unlimited VMs when all host cores are licensed. Standard: license by VM |
| Licensing by VM | Available for Standard and Datacenter with SA or subscription | Per-core VM licensing requires SA or subscription (since SQL Server 2022) |
| Failover and DR | Not applicable | With SA or subscription: one passive HA replica, one passive DR replica and one passive DR replica in Azure |
| Approx. list price | Standard $1,176 and Datacenter $6,771 per 16 cores | Standard about $3,945 and Enterprise about $15,123 per 2-core pack |
List prices are suggested prices published by Microsoft. Volume agreements, CSP and subscription pricing differ.
Most Windows Server and SQL Server cost sits on virtualized hosts. The hypervisor you choose changes the host license, how many Windows guests are covered and how costly it is to move workloads.
No separate hypervisor feeThe Hyper-V role is included with Windows Server Standard and Datacenter. If you already license hosts for Windows Server, the hypervisor itself is not an extra line item.
Host licensingLicense all physical cores in the host, subject to the 8-per-processor and 16-per-server minimums.
Standard vs DatacenterStandard covers two Windows VMs per full license set and can be stacked for more. Datacenter covers unlimited Windows VMs. Linux guests need no Windows license.
Keep the host leanWith Standard, running other server roles on the host operating system can use up one of the virtualization rights, so hosts are normally kept to Hyper-V and management only.
Free Hyper-V ServerMicrosoft Hyper-V Server 2019 was the last release of the free standalone product, supported until January 2029. It carries no Windows guest rights, so Windows VMs on it still need licenses.
Clusters and VM mobilityVMs that can move between hosts mean every host they may run on must be licensed for them, and license reassignment between hosts is restricted. Datacenter removes the stacking problem for dense clusters.
Per-VM licensing optionWindows Server can be licensed by VM for customers with SA or subscription. Microsoft revised its guidance on the minimums that apply in September 2025.
SQL Server on Hyper-VEither license all physical host cores (Enterprise with SA gives unlimited VMs), or license each VM with a 4-core minimum. Where a virtual core maps to more than one hardware thread, each thread is counted.
Hybrid and cloud-managed optionsWindows Server 2025 can be billed pay-as-you-go through Azure Arc. Azure Local runs on Hyper-V and is billed per physical core as an Azure service.
Broadcom moved VMware to per-core subscription bundles with a 16-core minimum per CPU, and announced a 72-core minimum order in April 2025; reports on whether that stayed in force differ, so verify current terms with your reseller. Many organizations are comparing Hyper-V and Azure Local as a result. Windows guests need licenses on any hypervisor, so the saving from leaving VMware comes from the hypervisor line, not from the Microsoft guest licenses. If Datacenter already covers a host, Hyper-V comes at no extra hypervisor cost. Fewer, denser hosts reduce core counts for both Microsoft and Broadcom licensing, but may raise failure-domain risk.
| Cost to compare | Stay on VMware | Move to Hyper-V or Azure Local |
|---|---|---|
| Hypervisor and management | Per-core subscription | Included with Windows Server, or the Azure Local per-core fee |
| Windows Server host and guests | Windows licenses for host cores and guests | Same licenses, with the Hyper-V role at no extra fee |
| SQL Server | Unchanged licensing rules | Unchanged licensing rules |
| Migration and operations | None | Migration effort, tooling, skills and backup changes |
These examples use published list prices and the rules above. They show how licensing decisions scale; they are not quotes.
| Server | Physical cores | Core licenses required | Standard list cost |
|---|---|---|---|
| 1 processor, 8 cores | 8 | 16 (server minimum) | $1,176 |
| 2 processors, 6 cores each | 12 | 16 (8 per processor) | $1,176 |
| 2 processors, 12 cores each | 24 | 24 | $1,764 |
| 2 processors, 16 cores each | 32 | 32 | $2,352 |
Standard list cost = core licenses ÷ 16 × $1,176.
One Standard license set costs $2,352 and covers 2 VMs. Datacenter costs $13,542 and covers unlimited VMs. Datacenter is cheaper from 11 VMs per host, on any host size, because both editions scale with core count.
| VMs on host | Standard sets needed | Standard cost | Datacenter cost |
|---|---|---|---|
| 4 | 2 | $4,704 | $13,542 |
| 8 | 4 | $9,408 | $13,542 |
| 10 | 5 | $11,760 | $13,542 |
| 11 | 6 | $14,112 | $13,542 |
| 16 | 8 | $18,816 | $13,542 |
| 20 | 10 | $23,520 | $13,542 |
Excludes CALs and Software Assurance.
Four hosts of 32 cores each run 15 Windows VMs per host (60 in total). Stacked Standard costs 8 sets × $2,352 × 4 hosts = $75,264. Datacenter on all four hosts costs $13,542 × 4 = $54,168: $21,096, or 28%, lower. This is conservative: with live migration, Standard would also have to cover VMs that can run on any host.
A gap of $89,424 per server, about $894,240 across ten similar servers
Before moving a workload, confirm it does not use Enterprise-only features and check Standard’s compute and memory limits. Recent versions moved features such as Resource Governor and Power BI Report Server into Standard.
| Scenario | Core licenses | List cost (Standard) |
|---|---|---|
| 20 SQL VMs, 2 vCPUs each (4-core minimum per VM) | 20 × 4 = 80 | 40 packs × $3,945 = $157,800 |
| Same workloads consolidated to 5 VMs of 8 vCPUs | 5 × 8 = 40 | 20 packs × $3,945 = $78,900 |
| Difference | 40 fewer cores | $78,900 |
Consolidation depends on technical feasibility, isolation and support requirements, so it is a modeled option, not a default.
A two-node SQL Server Standard availability group uses 8 vCPUs per node. Without failover rights both nodes are licensed: 16 cores, 8 packs, $31,560. With SA, the passive replica needs no license: 8 cores, 4 packs, $15,780, a saving of $15,780. SA is recurring, commonly cited at around 25% of the license price a year, here about $3,945. The replica must stay passive: running reads or workloads on it needs a license.
| Illustrative lever | Basis | List-price value |
|---|---|---|
| Windows: Datacenter for a dense 4-host cluster | Example 3 | $21,096 |
| SQL: Enterprise to Standard on 10 servers | Example 4 | $894,240 |
| SQL: consolidate 20 small VMs into 5 | Example 5 | $78,900 |
| SQL: use passive failover rights on one pair | Example 6 | $15,780 |
| Total illustrative license value | $1,010,016 |
List-price perpetual license value, not annual cash savings. Subscription, SA and CSP pricing change the cash profile. Real results depend on your estate.
Out-of-support serversMicrosoft sells Extended Security Updates as a bridge, but they add cost without extending the platform’s life.
Audit and true-up exposureServer products are a common focus of compliance reviews. Entering one without a documented topology and entitlement position leaves you responding to someone else’s numbers.
Compound cost creepNew hosts, larger core counts and spare VMs add license obligations that are easy to miss without continuous tracking.
Renewal leverage gapAt EA renewal, proposals lean on historical deployment assumptions. Verified counts let you commit to what you run, not what you might run.
Stretched IT teamsEngineering teams lose hours reconciling inventories and topology maps by hand.
Rythium’s proprietary tools ingest and parse server telemetry, hypervisor data and entitlement records at scale, and our licensing specialists turn the results into decisions you can defend.
Estate and topology mapHosts, clusters, VMs and instances with core counts, editions and versions.
Effective license positionWhat you must license vs what you own, by product, edition and agreement.
Right-sizing recommendationsEdition, core and density options with estimated list-price impact and technical risk.
Hypervisor and cluster reviewLicensing implications of your current platform and options such as Hyper-V, Azure Local or staying put.
SA and Hybrid Benefit reviewRights you hold but are not using, and Azure allocations that could be at risk.
End-of-support planServers and instances approaching support dates, with upgrade, migrate or ESU options.
Audit-ready evidence packDocumented position, assumptions and renewal scenarios.
Software Assurance (SA) is easy to treat as a renewal line item. Used well, it unlocks rights that change what you need to buy.
| Right | What it gives | Watch out |
|---|---|---|
| Passive failover | SQL Server: one passive HA replica, one passive DR replica and one passive DR replica in Azure, with no extra license, when covered by SA or subscription. | Replicas must be passive. Active workloads need licenses. |
| Azure Hybrid Benefit | Use Windows Server and SQL Server licenses with active SA or subscription on Azure. For Windows Server, each set of 16 core licenses with SA covers up to 16 virtual cores across no more than two Azure VMs. | Lapsed SA means the benefit must be removed. Allocating more VMs than your licenses support is a compliance risk. |
| Per-VM licensing | Windows Server and SQL Server can be licensed by virtual machine when covered by SA or subscription. | Minimums apply (4 cores per SQL VM). Check the current Windows per-VM minimums. |
| Unlimited virtualization | SQL Server Enterprise with SA, with all host cores licensed, covers unlimited VMs. | Only pays off on dense hosts with many SQL VMs. |
| Flexible Virtualization Benefit | With SA or subscription, deploy licenses on Authorized Outsourcers’ servers, shared or dedicated. | Some large cloud providers are excluded. Check the current outsourcer list. |
| Power BI Report Server | SQL Server 2025 Standard and Enterprise customers can run it without extra licenses, even without active SA. | Earlier versions needed Enterprise with active SA. |
Many estates run SQL Server 2016 on Windows Server 2016, so two support deadlines land within months. Each path has a different licensing profile:
| Path | Licensing considerations | Best when |
|---|---|---|
| Upgrade in place or on new hosts | Move to Windows Server 2025 and SQL Server 2022 or 2025. Re-count cores, review editions and re-check SA coverage. | A hardware refresh is due and you want to stay on-premises. |
| Move to Azure VMs | Azure Hybrid Benefit can reduce Windows Server and SQL Server software charges if you hold active SA. | SA is active and the workload suits cloud. |
| Replatform to a managed database | Azure SQL Managed Instance can retire both the Windows and SQL lifecycle questions in one project. | The application is compatible and the team wants less administration. |
| Buy Extended Security Updates | Pays for time, not a future. SQL Server 2016 ESU runs in three annual terms to July 2029. | You need a short bridge to finish a migration. |
Lower license costRemove unneeded cores, edition over-provisioning and unused capacity, typically reducing license requirement by 5 to 20%, based on Rythium engagements.
Avoid non-complianceFind and fix licensing gaps, such as missed core minimums, unlicensed cluster hosts, active replicas and Hybrid Benefit over-allocation, before an audit or true-up does.
A defensible positionA documented baseline of what you run and what you own, supported by evidence.
Stronger negotiationsNegotiate EA, CSP or cloud migration terms using verified data.
Better hybrid decisionsAlign on-premises and Azure licensing so you do not pay twice for the same software.
Clear platform choicesCompare hypervisor and cluster options on total cost, not one line.
A plan for end-of-support serversPrioritized by date, risk and cost.
Metadata onlyCollection covers inventory, configuration and utilization metadata, not database contents.
Low-impact collectionCollection is designed not to affect production performance.
Your infrastructureWe work through remote access on your infrastructure, and all data stays on it.
GovernanceNDA and DPA available on request.
Proprietary processing powerSpecialized tools and licensing expertise cut through complex topologies and hypervisor layers to deliver faster, cleaner reporting.
IndependentWe do not resell any publisher’s licenses or earn income from publishers. Our focus is our customers.
Hypervisor-awareWe analyze licensing together with your Hyper-V, VMware and Azure Local design, not in isolation.
Low-disruption methodTelemetry collection is designed to avoid impact on networks, production databases and daily operations.
What we needRemote access to a VM set up for telemetry data and our tools, secure credentials to discover deployed inventory and hypervisor data, plus an infrastructure contact and a licensing contact.
What you decideEvery recommendation is yours to accept, change or reject. We do not alter your environment.
Also see all Rythium Microsoft services and Microsoft 365 Optimization.
The Hyper-V role is included with Windows Server Standard and Datacenter. You pay for the Windows Server licenses on the host, which also cover the Windows guests according to the edition and the number of license sets.
Two per full license set on a host, and you can stack sets for more. Datacenter covers unlimited VMs. On a 32-core host Datacenter becomes cheaper from 11 VMs at list prices.
It depends on VM count and density. Enterprise with SA on a fully licensed host covers unlimited VMs. Standard in virtualized environments is licensed by VM, with a 4-core minimum per VM.
Windows guests still need licenses on any hypervisor. What changes is the hypervisor cost and cluster design. We model both together.
Microsoft Hyper-V Server 2019 was the final release. It remains supported until January 2029 but has no Windows guest rights.
SQL Server 2016 support ended in July 2026 and Windows Server 2016 ends in January 2027. Extended Security Updates are available as a paid bridge. We help you choose between upgrading, moving or buying ESU.
No. Collection is designed for low impact, and recommendations are yours to approve.
No. Rythium is independent and does not resell publisher licenses or earn income from publishers.
We charge a fixed fee for the assessment, a success-based fee or a hybrid, case by case, depending on the scope and the deliverables you need. Contact us for a scoped quote and tell us your preference.
Talk to our licensing specialists about your estate, platform plans and renewal date. We will show you what you run, what you must license and where the savings are.
Cookies on rythium.com
We use essential cookies to make this site work, and additional cookies to measure visits and our ads. You can reject the additional ones or choose which to keep. Privacy Policy