Editorial photograph supporting the SQL Server licensing pillar article
Pillar · Microsoft · SQL Server

SQL Server licensing. Cores, CALs, SA, and the cloud overlay.

SQL Server licensing punishes the inattentive. Cores, CALs, Software Assurance, virtualization, HA topology, and the cloud overlay each carry rules that Microsoft audits use to score gaps.

Contact Us Microsoft Practice
500+Enterprise clients
$2B+Under advisory
Gartner Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

SQL Server licensing punishes the inattentive. Cores, CALs, virtualization, HA secondaries, and cloud all carry rules that audits exploit.

Key takeaways

  • Two metrics survive. SQL Server licenses on either per core or Server plus CAL. The two are not interchangeable mid term.
  • Software Assurance is the lever. SA unlocks version upgrades, license mobility, Azure Hybrid Benefit, and disaster recovery rights.
  • Virtualization rules are strict. Each VM running SQL Server needs core licenses sized to the assigned virtual cores, minimum four.
  • Passive HA secondary is free with SA. Active secondaries require full licensing. The rule is audited.
  • Azure Hybrid Benefit moves 30 to 55 percent. SA covered licenses unlock AHB discount on Azure SQL deployments.
  • 2022 release added new compliance traps. Pay as you go option on Azure Arc, ledger features, and the new audit telemetry change the posture.
  • The audit gap is consistent. Most enterprises run between 8 and 22 percent short of SQL Server compliance entitlement.

SQL Server licensing has stayed structurally consistent for a decade. The detail has not. Each release adds rules that audits use to score gaps.

This pillar maps the licensing model end to end. Editions, metrics, Software Assurance, virtualization, HA and DR, cloud overlay, and audit posture.

Read the related Microsoft knowledge hub and the Microsoft advisory service for the wider context.

What are the SQL Server editions and where does each fit?

The five editions

  • Enterprise. Full feature set. Per core only.
  • Standard. Core production workloads. Per core or Server plus CAL.
  • Web. Public facing only. Service provider channel.
  • Developer. Free, non production.
  • Express. Free, capped at 10 GB and limited features.

Edition fit by workload

Enterprise edition fits mission critical OLTP, large analytics workloads, and any deployment needing Always On Availability Groups with multiple secondaries.

Standard edition fits departmental OLTP, smaller analytics, and most line of business databases under 128 GB.

What forces a downgrade decision

Standard edition caps memory at 128 GB and TempDB at limited core counts. Beyond those limits, Enterprise is the only option.

Many buyers run Enterprise where Standard suffices. The audit usually surfaces the opposite, Standard running Enterprise features.

How do SQL Server Core and CAL metrics work in 2026?

Per core licensing

Per core licensing sells in two core packs. Each pack covers two physical or virtual cores. The minimum per server is four cores.

Per core licensing covers unlimited users. The metric scales by hardware, not by population.

Server plus CAL licensing

  • Server license per instance. One license covers the server or virtual machine.
  • CAL per user or per device. Each named user or device accessing the server needs a CAL.
  • Standard edition only. Enterprise edition is per core only.
  • Cap on Server plus CAL workloads. Not viable for internet facing or large user populations.

Virtualization rules

Per core licensing in virtualized environments licenses the assigned virtual cores per VM. Minimum four cores per VM.

Fully licensing the host unlocks unlimited VMs running SQL Server on that host. Software Assurance is required.

SQL Server licensing decision matrix

Scenario Metric Edition fit SA requirement
Mission critical OLTPPer coreEnterpriseRequired
Departmental OLTPPer core or Server CALStandardRecommended
Analytics workloadPer coreEnterpriseRequired
Azure SQL Managed InstanceAzure SKU + AHBEnterprise or StandardRequired for AHB
Dev / testDeveloper editionDeveloperNot applicable
Reporting layerPer core or Server CALStandardRecommended

What does SQL Server Software Assurance actually unlock?

What SA unlocks

  • Version upgrade rights. Move to the next SQL Server release without buying new licenses.
  • License mobility. Move licenses to authorized outsourcers and to many cloud providers.
  • Azure Hybrid Benefit. Discount on Azure SQL services for SA covered licenses.
  • Passive secondary rights. One passive failover instance with no additional license.
  • Disaster recovery rights. Cold and warm DR scenarios at no extra license.
  • New version rights. Use a prior version under a newer license.

When SA pays off

SA cost is approximately 25 percent of license cost per year. SA pays off if the customer plans a version upgrade, runs Azure SQL, or relies on HA failover.

Most enterprise SQL Server estates need SA. The exception is fixed legacy estates with no upgrade or cloud trajectory.

SA renewal mechanics

SA renews on the EA cycle. Lapse and reinstatement is expensive, typically 1.5 to 2 times the SA price.

Buyers should map SA on every SQL Server license at renewal and decide line by line.

How do SQL Server cloud overlay rules work?

Azure Hybrid Benefit math

AHB applies SA covered SQL Server licenses against Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure VM.

Cost reduction runs 30 to 55 percent compared to license included Azure SKUs. The discount applies for the full license term.

License mobility to AWS and GCP

  • AWS. SA covered licenses qualify for License Mobility on AWS dedicated hosts or shared tenancy with conditions.
  • Google Cloud. SA licenses qualify under specific Compute Engine and Cloud SQL configurations.
  • Listed providers only. Microsoft maintains a list of authorized outsourcers. Off list providers do not qualify.
  • The trap. Customers move workloads then discover license mobility does not apply to their provider configuration.

Azure pay as you go on Arc

SQL Server 2022 added pay as you go billing through Azure Arc. Customers can run SQL Server on premises and pay per vCore per hour.

The model fits variable workloads. Fixed estates rarely benefit. The metric is reported through Arc telemetry, which audits can read.

Where the common advice on SQL Server SA is wrong

The standard Microsoft pitch is that Software Assurance pays back through version upgrade rights and is therefore a default add on for every SQL Server estate. We disagree. In roughly five out of eight SQL Server estates we have audited, the SA premium exceeded the version upgrade value across the term because most enterprises run prior version SQL Server for five to seven years before upgrading. The SA value lives in the disaster recovery rights, Azure Hybrid Benefit eligibility, and license mobility. Buy SA against those three specific use cases, not as an undifferentiated default. The economics often favor SA on production cores and skip SA on test or development cores.

Editorial photograph of a database team reviewing SQL Server core inventory and Software Assurance coverage across production and DR estates
SA decisions should be made at the core, not the contract. Production cores with HA or AHB exposure earn SA. Test and lab cores rarely do.
38
SQL Server audit defenses and reviews
17%
Median compliance gap on first inventory
42%
Median Azure Hybrid Benefit recovery on cloud SQL

Source: Redress Compliance advisory engagement file, 2024 to 2025.

SQL Server compliance is not a hardware count. It is a posture. The buyer who anchors HA topology, edition usage, and cloud overlay wins the audit.

How does SQL Server HA and DR licensing work?

Passive secondary rule

One passive secondary instance is free under Software Assurance. The secondary must not serve queries, accept backups, or run any active workload.

The rule is the most common audit finding. Readable secondaries are not passive.

Active secondary licensing

  • Readable secondaries. Each active secondary needs full licensing.
  • Backup secondaries. Backups offloaded to a secondary count as active use.
  • DBCC CHECKDB secondaries. Integrity checks on a secondary count as active use.
  • Log shipping standby. Standby instances open for queries count as active.

DR licensing scenarios

Cold DR is free under SA. Warm DR with no active workload is also free.

Hot DR with active queries is not free. Each hot DR instance needs full licensing.

What are the common SQL Server audit findings?

How Microsoft audits surface SQL Server

SQL Server audits typically use MAP Toolkit or SCCM extraction to inventory installed instances and core counts.

The audit reconciles inventory against EA entitlement. The gap surfaces as a true up bill at list.

Common findings

  • Readable secondaries. Treated as passive but configured as readable.
  • Standard edition running Enterprise features. Compression, partitioning, audit, or always on AG.
  • VM core sprawl. Virtual cores increased beyond contracted entitlement.
  • Mobility to wrong provider. SA mobility used on non listed cloud configurations.
  • Developer in production. Developer edition used for production reporting or test data.

Defensive posture

Buyer side defense rests on a current Effective License Position. Inventory by edition, by core count, by HA topology.

Anchor the ELP every six months. Run a self audit before Microsoft does. The Microsoft EA renewal is the optimal window.

Suggested reading

What should a buyer do next?

  1. Inventory every SQL Server instance. Edition, core count, HA role, virtualization, cloud overlay.
  2. Reconcile to entitlement. Match the inventory line by line to the active EA entitlement.
  3. Score the passive secondary rule. Any readable secondary needs to come back into compliance.
  4. Map SA coverage. Each license should have SA mapped or removed by intent.
  5. Run the AHB math. Calculate Azure SQL savings if SA covered licenses moved.
  6. Anchor the cloud mobility list. Each cloud SQL workload should match an authorized provider configuration.
  7. Run a self audit before the EA renewal. Use the renewal as the leverage window.

Frequently asked questions

How is SQL Server licensed in 2026?

SQL Server is licensed per core or Server plus CAL. Enterprise edition is per core only. Standard edition supports both. Each VM running SQL Server needs core licenses sized to virtual cores, minimum four.

Is the passive secondary really free with Software Assurance?

Yes, one passive failover secondary is free under SA. The secondary must not serve queries, run backups, or accept any active workload. Readable secondaries break the rule.

Does Azure Hybrid Benefit apply to all SQL Server licenses?

AHB applies only to SQL Server licenses with active Software Assurance. The benefit covers Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure VM.

Can I use SQL Server SA mobility on AWS?

Yes, SA covered licenses qualify for License Mobility on AWS dedicated hosts or shared tenancy with specific conditions. Microsoft maintains an authorized provider list. Off list providers do not qualify.

What is the difference between Standard and Enterprise edition?

Standard caps memory at 128 GB and limits TempDB scale. Enterprise unlocks full feature set including Always On Availability Groups with multiple secondaries, partitioning, and advanced compression.

How often do Microsoft audits surface SQL Server gaps?

SQL Server audits surface gaps in approximately 75 percent of enterprise estates. Common gaps run between 8 and 22 percent of installed entitlement. The most common finding is readable secondaries treated as passive.

How does Redress engage on SQL Server compliance?

Redress runs SQL Server advisory inside the Vendor Shield subscription and Microsoft Renewal Program. Engagements cover ELP build, audit defense, AHB math, and SA renewal decisioning.

What does Redress recommend as the first move on this topic?

Open with an inventory and entitlement baseline before any vendor conversation. Pull trailing twelve months of usage data, score it against contracted scope, and document the gap. The single most common reason buyers leave money on the table is opening the negotiation without a defensible baseline. The buyer side calendar starts at 270 days out, not at 60.

Microsoft EA Renewal Playbook

The full microsoft ea renewal playbook framework from the Microsoft Practice.

Microsoft renewal moves, EA framework, M365 SKU framework, Copilot framework, and 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.

No spam. We will only email you about this download. Privacy.
Run the Microsoft 365 license optimizer against your estate in under five minutes.
Open the Tool →
8-22%
Average gap
55%
AHB ceiling
500+
Enterprise clients
$2B+
Under advisory
100%
Buyer Side

SQL Server licensing is a posture, not a count. Edition fit, HA topology, and the cloud overlay carry more value than any rate discount Microsoft ever offered.

Former Microsoft Licensing Compliance Lead
On the buyer side, 28 SQL Server audits defended in 2025
Deep Library

More on this topic.

Microsoft Practice →
Microsoft Knowledge Hub
Microsoft · Hub
Microsoft Knowledge Hub
Core Microsoft hub for buyers.
14 min read
Microsoft EA Renewal Playbook
Microsoft · Playbook
EA Renewal Playbook
EA renewal negotiation playbook.
22 min read
Microsoft Advisory Service
Microsoft · Service
Microsoft Advisory
Buyer side Microsoft advisory.
9 min read
Seven EA renewal mistakes
Microsoft · Article
Seven EA Renewal Mistakes
Common EA mistakes to avoid.
11 min read
Editorial boardroom interior

The advisor your vendors do not want.

500+ enterprise clients. 11 vendor practices. Gartner recognized. One conversation can change what you pay for the next three years.

Microsoft intelligence, monthly.

SQL Server, M365, Azure, EA, and Copilot lessons from every Microsoft engagement we run.