SQL Server licensing. Cost down, compliance intact.

SQL Server licensing costs fall 30 to 50 percent when edition choice, core counting, virtualization rules, and Azure Hybrid Benefit are decided deliberately instead of inherited.

Should you license SQL Server per core or with CALs?

Per core licensing wins when users are uncountable or numerous; Server plus CAL wins for small, known user populations, with the crossover typically between 25 and 40 users per server. Microsoft publishes the editions and models on its SQL Server 2022 pricing page.

Per core requires a minimum of four core licenses per physical processor. Core licenses sell in two packs, and every physical core on the machine counts unless virtualization rules apply.

Where do estates get the model wrong?

• Internet facing on CALs: external users cannot be CAL counted; those servers must be per core.
• Per core for ten users: small internal databases often overpay on per core out of uniformity.
• Mixed without mapping: nobody documents which server runs which model, and audits exploit it.

When is Standard edition enough instead of Enterprise?

Standard edition covers most OLTP workloads: it carries availability groups in basic form, fills the memory needs of mid sized databases, and costs roughly a quarter of Enterprise per core. The feature split is documented in the editions comparison; Enterprise earns its premium only for specific features and scale.

How much does edition rightsizing save?

Enterprise lists at roughly four times Standard per core. In our reviews, moving eligible workloads down cut those line items by 50 to 65 percent after repurchase math.

How do virtualization rules change SQL Server costs?

Two legitimate paths exist: license individual VMs with a four core minimum each, or license all physical cores with Enterprise and active Software Assurance for unlimited virtualization on that host. The rules live in the Microsoft Product Terms.

• Dense hosts favor unlimited: above roughly 10 SQL VMs per host, full physical licensing with SA usually wins.
• Sparse VMs favor per VM: a few VMs on a big host should not license every physical core.
• vMotion needs mobility: moving VMs across hosts without License Mobility rights creates audit findings.

Why do audits find virtualization errors so often?

Because cluster configurations drift after licensing decisions are made. A host added to the cluster, or DRS rebalancing VMs, silently changes the license requirement.

How does Azure Hybrid Benefit cut SQL costs?

Azure Hybrid Benefit lets SQL Server licenses with active Software Assurance cover Azure SQL workloads, cutting pay as you go costs by 30 to 55 percent. Microsoft documents the exchange rates on its Azure Hybrid Benefit page.

The benefit converts on premises entitlements into Azure capacity at defined ratios, with four core packs converting most efficiently into vCore based services. Dual use rights cover the 180 day migration window.

What should you check before applying AHB?

• SA is active: the benefit requires current Software Assurance or subscription licenses.
• No double counting: a license applied in Azure cannot also cover on premises use past the migration window.
• Centralize allocation: AHB assigned ad hoc by engineers double spends entitlements.

Where the common advice on SQL Server licensing is wrong

The standard renewal advice is to keep Software Assurance on everything because dropping it is irreversible. We disagree. In roughly 16 of the 25 plus estates Morten Andersen reviewed in 2024 to 2025, SA on stable, physical, non virtualized SQL workloads bought rights the estate never used, adding 25 percent annually for mobility and upgrade benefits with no consumption. SA pays where virtualization, Azure mobility, or version currency genuinely matter; elsewhere it is insurance against nothing. The buyer side move is to map SA benefits to actual architecture per workload, keep it where the rights are consumed, and let it lapse where they are not.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Inventory every SQL instance: edition, cores, host, cluster, and model.
2. Flag Enterprise instances whose features fit inside Standard.
3. Recount virtualization licensing against current cluster configuration.
4. Map Software Assurance benefits to actual per workload consumption.
5. Centralize Azure Hybrid Benefit allocation under one owner.
6. Run the corrected count before Microsoft does, then take it to renewal.

White Paper · Microsoft

Windows Server and SQL Hybrid Licensing

Read it free.

Read the white paper

Frequently asked questions

When does per core beat Server plus CAL for SQL Server?

Above roughly 25 to 40 users per server, or whenever users are uncountable, including all internet facing workloads. Small known populations still favor CALs.

How much cheaper is SQL Server Standard than Enterprise?

Standard lists at roughly a quarter of Enterprise per core. Edition rightsizing cut eligible line items by 50 to 65 percent in our 2024 to 2025 reviews.

How does unlimited virtualization licensing work?

License all physical cores on the host with Enterprise edition and active Software Assurance, and every SQL VM on that host is covered.

What is Azure Hybrid Benefit worth on SQL workloads?

30 to 55 percent against pay as you go rates. It requires active Software Assurance and converts on premises core licenses into Azure vCore capacity.

Why is SQL Server the top audit finding generator?

Core counting and virtualization rules drift after deployment. Cluster changes silently alter requirements, and 1 in 2 estates we reviewed carried count errors.

Should Software Assurance be kept on all SQL licenses?

No. Keep SA where virtualization rights, license mobility, or Azure plans consume its benefits. On stable physical workloads it often buys nothing.