SQL Server 2016 extended support ended on 14 July 2026. Is your estate ready?
SQL Server is licensed per core, with a 4-core minimum per processor and per VM, and Enterprise costs about four times Standard. We count your instances against Microsoft’s rules and show where you can pay less.
5–20%Typical reduction in server license requirement, based on Rythium engagements
| Product | Per | List |
|---|---|---|
| SQL Server Standard | 2 cores | $3,945 |
| SQL Server Enterprise | 2 cores | $15,123 |
Volume agreements, CSP and subscription pricing differ.
SQL Server is licensed by cores, editions, virtual machines and rights that depend on whether you hold Software Assurance. Small mistakes in any of these multiply across instances and clusters. The most common traps:
Core-counting errorsSQL Server needs at least 4 core licenses per processor and per virtual machine, so many small VMs can cost more than a few larger ones.
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).
Host or VM, chosen badlyLicensing SQL Server per VM where host-level licensing would cost less, or licensing whole hosts for a handful of VMs.
Active replicasA secondary replica that serves reads or reports is no longer passive and needs licenses.
Unused Software Assurance rightsPassive failover and disaster recovery rights, Azure Hybrid Benefit and per-VM licensing options that go unclaimed.
Out-of-support instancesSQL Server 2016 extended support ended in July 2026. 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 | SQL Server 2025 |
|---|---|
| Licensing metric | Per core (Standard and Enterprise), or Server + CAL for Standard |
| Minimum cores | 4 core licenses per physical processor, and 4 per VM when licensing by VM |
| Pack sizes | 2-core packs |
| Virtualization rights | Enterprise with active SA: unlimited VMs when all host cores are licensed. Standard: license by VM |
| Licensing by VM | Per-core VM licensing requires SA or subscription (since SQL Server 2022) |
| Failover and DR | With SA or subscription: one passive HA replica, one passive DR replica and one passive DR replica in Azure |
| Approx. list price | 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.
License the hostLicense all physical host cores. Enterprise with SA then covers unlimited SQL Server VMs on that host.
License each VMLicense each VM’s virtual cores, with a 4-core minimum per VM. Where a virtual core maps to more than one hardware thread, each thread is counted.
Any hypervisorThe rules are the same on Hyper-V, VMware or Azure Local. Leaving VMware does not change SQL Server licensing.
Density decidesMany SQL VMs on one host favor licensing the host with Enterprise and SA; a few VMs favor licensing by VM.
These examples use published list prices and the rules above. They show how licensing decisions scale; they are not quotes.
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.
A saving of $15,780, against SA of about $3,945 a year
Out-of-support instancesMicrosoft 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 instances, larger VMs and replicas that quietly start serving reads add license obligations that are easy to miss without continuous tracking.
A weaker renewal positionAt EA renewal, proposals lean on historical deployment assumptions. Verified counts let you commit to what you run, not what you might run.
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.
Instance mapEvery SQL Server instance with edition, version, cores and the host or VM it runs on.
Effective license positionWhat you must license vs what you own, by edition and agreement.
Right-sizing recommendationsEdition, core and consolidation options with estimated list-price impact and technical risk.
SA and Hybrid Benefit reviewFailover rights and Azure allocations you hold but are not using, or are over-using.
End-of-support planInstances approaching support dates, with upgrade, migrate or ESU options.
Software Assurance (SA) is easy to treat as a renewal line item. Used well, it brings rights that change what you need to buy.
| Right | What it gives | Watch out |
|---|---|---|
| Passive failover | 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 SQL Server licenses with active SA or subscription on Azure. | Lapsed SA means the benefit must be removed. |
| 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. |
| Per-VM licensing | SQL Server can be licensed by virtual machine when covered by SA or subscription. | A 4-core minimum applies to each VM. |
| 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. |
| Path | Licensing considerations | Best when |
|---|---|---|
| Upgrade in place or on new hosts | Move to 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 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.
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.
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.
Remote 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.
Every recommendation is yours to accept, change or reject. We do not alter your environment.
Per core for Standard and Enterprise, with at least 4 core licenses per physical processor, and 4 per VM when licensing by VM, sold in 2-core packs. Standard can also be licensed as Server + CAL.
Enterprise costs roughly four times Standard per core and adds features and higher compute and memory limits. With SA and all host cores licensed, Enterprise covers unlimited VMs. Many workloads run on Standard; recent versions moved features such as Resource Governor and Power BI Report Server into Standard.
SQL Server Standard can be licensed per core, or per server with a CAL for every user or device that uses it. Enterprise is licensed per core only.
Microsoft’s suggested list prices are about $3,945 for Standard and $15,123 for Enterprise per 2-core pack. A 16-core server costs about $31,560 on Standard and $120,984 on Enterprise. Volume agreements, CSP and subscription pricing differ.
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.
Not if it stays passive and you hold SA or subscription: one passive HA replica, one passive DR replica and one passive DR replica in Azure are covered. A replica that serves reads or reports needs licenses.
Developer edition is free for development and testing, never for production. Production workloads need Standard or Enterprise licenses.
SQL Server 2016 extended support ended in July 2026. Extended Security Updates are available as a paid bridge until July 2029. 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 instances, 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