SQL Server is the single richest source of findings in a Microsoft audit. Per core minimums, virtualization rules, and edition feature use are where the claims are built, and where a prepared buyer protects the most value.
SQL Server is the single richest source of findings in a Microsoft audit. Per core minimums, virtualization rules, and edition feature use are where the claims are built, and where a prepared buyer protects the most value.
SQL Server licensing is complex by design. The per core metric, the edition split, and the virtualization rules combine into a surface where small misreadings become large numbers.
This guide covers the core rules, the virtualization trap, mobility and failover, and the buyer side moves that hold the line in a SQL Server audit.
SQL Server is licensed per physical core on the server, or per virtual core in a virtual machine, with a minimum of four cores per licensed instance.
You license all physical cores in the server when licensing at the host level. Confirm the current rules against the SQL Server 2022 pricing and licensing page.
Standard and Enterprise carry different rights and very different prices. Enterprise unlocks features that Standard does not. Running those features on a Standard license is a finding waiting to happen. See the edition and feature documentation.
Every licensed instance requires at least four core licenses, even on smaller hardware. The detail sits in the Microsoft Product Terms. Small servers do not reduce below this floor.
Where SQL Server findings come from
| Finding | Root cause | Buyer side fix |
|---|---|---|
| Edition mismatch | Enterprise features on Standard | Disable the feature or true up to Enterprise |
| Core shortfall | Physical cores exceed licensed cores | Reconcile cores per host before review |
| Virtualization gap | VM movement without host licensing | License the cluster or pin with Software Assurance |
| Failover breach | Passive node used actively | Confirm Software Assurance and passive use |
Because virtual machines move, and licensing assumes they do not unless you have the right to move them. That right comes from Software Assurance.
Licensing all physical cores on a host with Enterprise edition and Software Assurance allows unlimited SQL Server virtual machines on that host. Without it, you license each virtual machine.
License Mobility through Software Assurance lets you move SQL Server licenses across servers more often than every ninety days, and into authorized cloud environments. Without Software Assurance, the ninety day reassignment rule applies.
A virtual machine that can migrate across an unlicensed cluster exposes every host it could land on. Auditors price the worst case. Pin the workload or license the cluster.
The standard advice is to license conservatively at the host with Enterprise edition and Software Assurance everywhere, so you never face a finding. We disagree. In our engagements that approach routinely overlicensed estates by a wide margin, because much of the workload ran fine on Standard or sat on hosts that never needed cluster wide rights. The buyer side move is to map each workload to the edition and mobility right it actually uses, license the host fully only where virtual machines truly roam, and treat blanket Enterprise plus Software Assurance as a decision to justify, not a default.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
SQL Server is where Microsoft audits are won or lost. Reconcile the editions and the cores before anyone else counts them for you.
You reconcile editions, cores, and Software Assurance status before the review opens, and you separate genuine shortfall from measurement error.
Map every instance to the features it actually runs. Where Standard is sufficient, document it. Where Enterprise features run, decide to disable or true up.
Software Assurance underpins mobility and failover rights. Confirm coverage per license before relying on either. Lapsed coverage removes the right.
Passive secondaries are licensed only when truly passive and backed by Software Assurance. As set out in the failover cluster documentation, a secondary serving reads or reports is active and must be licensed.
SQL Server is licensed per core, either per physical core when licensing at the host or per virtual core in a virtual machine, with a minimum of four core licenses per instance. Standard and Enterprise editions carry different rights and prices.
Running Enterprise edition features on a Standard license is the most expensive common finding, followed by core shortfall where physical cores exceed licensed cores. Together they account for the bulk of SQL Server claims in most reviews.
Virtual machines can migrate across hosts. Without licensing the full physical host or holding Software Assurance for mobility, a migrating instance can put every host it could land on into scope, and auditors price the worst case.
Software Assurance enables License Mobility, which allows licenses to move across servers more frequently than every ninety days and into authorized clouds. It also underpins passive failover rights. Without it, the ninety day reassignment rule applies and failover rights are limited.
Only if it is truly passive and you hold Software Assurance. A secondary that serves reads, reporting, or backups is considered active and must be licensed. Many estates breach this by using the secondary for reporting.
Yes. The auditor opening figure reflects list price and the widest reading of deployment. Reconciling editions, core counts, and Software Assurance status typically reduces the defensible claim well below the opening number before any commercial discount.
Yes. Every licensed SQL Server instance requires at least four core licenses regardless of the hardware. Smaller servers do not allow you to license below that floor.
Build an entitlement record reconciled to deployment before any review. Inventory editions, versions, and cores, confirm Software Assurance, validate failover use, and identify migrating virtual machines. A prepared position caps exposure and shortens the review.
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the full Microsoft estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
In nearly every Microsoft review we defend, SQL Server is the largest single line in the claim. It is also the line where preparation recovers the most.
