A buyer side guide to SQL Server 2022 licensing in 2026. Per core versus Server plus CAL, edition choice, Software Assurance rights, Azure Arc billing, and where the cost really sits.
SQL Server 2022 is licensed either per core or by Server plus CAL, and the choice between those two models, plus the edition you pick and whether you carry Software Assurance, drives the real cost far more than the headline per core price.
Quick answer
SQL Server 2022 is licensed per core or Server plus CAL. Edition, model, and Software Assurance set the real cost. Here are the rules and the buyer side moves.
This pillar is for buyers planning a SQL Server 2022 estate or renewal. Read it with the SQL Server licensing pillar, the Windows and SQL Server practical guide, and the Microsoft Knowledge Hub.
There are two models. Per core suits server workloads with many or unknown users. Server plus CAL suits smaller, countable user populations.
Microsoft documents both on its SQL Server 2022 pricing page. The model you choose is locked per license, so the decision matters at purchase time.
Per core licenses every physical core on the server, with a minimum of four cores per instance. Licenses are sold in two core packs.
Server plus CAL licenses the server once and then a Client Access License for each user or device. It wins when the user count is small and stable.
Edition choice is the biggest single cost lever. Enterprise costs several times Standard per core, so deploying Enterprise where Standard would serve is the classic over spend.
SQL Server 2022 editions and models, illustrative list per core per year
| Edition | Models | Indicative list per core | Best fit |
|---|---|---|---|
| Standard | Per core or Server plus CAL | 3,586 dollars | General workloads |
| Enterprise | Per core only | 13,748 dollars | Mission critical, large scale |
| Web | Per core, hosters | Low, SPLA only | Public web workloads |
| Express | Free | 0 dollars | Small, capped databases |
Software Assurance adds rights that change the economics. It enables License Mobility, free passive failover, and the Azure Hybrid Benefit.
SQL Server 2022 can be billed hourly per core through Azure Arc, turning a capital purchase into an operating cost. Microsoft describes the model in its SQL Server enabled by Azure Arc documentation.
The standard advice is to standardize on Enterprise Edition for simplicity and headroom. We disagree. In roughly 1 in 3 estates we reviewed, Enterprise was deployed where Standard would have met every requirement.
The buyer side move is to license each workload to its real need and reserve Enterprise for the features that genuinely require it, such as advanced availability groups and unlimited virtualization. Simplicity is not worth several times the per core price.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
SQL Server cost is decided before you install anything. Pick the edition for the workload, not the org, and the per core price stops being the problem.
The real question is the breakeven, not the definition. Standard offers both models; Enterprise is per-core only. Under per-core, every server carries a 4-core minimum per instance and cores sell in 2-core packs ($3,945 each), so the floor for any Standard box is two packs, $7,890, and that grants unlimited users. Under Server+CAL you pay $989 for the server plus $230 per user or device CAL. Set them equal — $989 + $230 × CALs = $7,890 — and the breakeven is about 30 users on a 4-core server; on an 8-core server it climbs to about 64.
Edition, model and list price
Microsoft list / ELP, pre-discount. Real EA/CSP transaction prices run materially lower.
| Edition | Models | List price | Key limits |
|---|---|---|---|
| Enterprise | Per-core only | $15,123 / 2-core pack | Unlimited cores/RAM; Unlimited Virtualization (with SA) |
| Standard (per-core) | Per-core | $3,945 / 2-core pack | 24 cores / 128 GB buffer pool cap |
| Standard (Server+CAL) | Server + CAL | $989 server + $230/CAL | Best for small, known user counts |
| Developer / Express | Free | $0 | Non-production / limited scale |
Per-core vs Server+CAL breakeven (Standard)
| Server size | Per-core cost (unlimited users) | Server+CAL breakeven |
|---|---|---|
| 4 cores (minimum) | 2 packs = $7,890 | ~30 users |
| 8 cores | 4 packs = $15,780 | ~64 users |
| Web / public app | Per-core | Users uncountable — always per-core |
Server+CAL is almost always cheaper for small, known populations (departmental apps, back-office ERP with 15 to 40 named users), while per-core wins for public-facing or unknown-user workloads. The trap is multiplexing: pooling a web or middleware tier in front of SQL does not reduce CAL requirements — every distinct human or device that touches the data indirectly still needs a CAL. The moment users are unbounded or an auditor could not enumerate them, default to per-core, because a failed CAL count is treated as unlicensed use.
Picking wrong here is one of the most expensive SQL mistakes. Per-VM licensing covers the virtual cores allocated to each SQL VM (again a 4-core minimum), which suits a few SQL VMs on a large shared cluster. Per-host licensing covers every physical core on the host and then permits any number of SQL VMs on it. The pivotal named right is Unlimited Virtualization, available only with Enterprise licensed per physical core and active Software Assurance. Once every physical core on a host — or a whole cluster — is licensed Enterprise+SA, you run unlimited instances and move them freely across that boundary.
Two numbers matter: SQL 2022 counts physical cores with a 4-core minimum per processor, and — unlike the 2008–2012 era — there is no core-factor table, so every physical core counts as 1.0. Ignore any quote that applies a 0.75 multiplier. Model density: a cluster running many SQL VMs, or relying on vMotion / Live Migration mobility, frequently makes Enterprise-per-host+SA cheaper than licensing dozens of VMs, and it removes the compliance risk of dynamic VM movement. VM mobility without SA is a compliance landmine — License Mobility is the SA benefit that legally permits reassigning licenses more often than every 90 days.
SA adds roughly 25 to 30 percent per year, so buy it where the rights pay for themselves rather than reflexively. The benefits with real economic weight: free passive/failover servers; License Mobility; Unlimited Virtualization on Enterprise+SA; Azure Hybrid Benefit; version upgrade rights to SQL 2025 and beyond; and unlimited containerization when all cores are licensed.
Software Assurance benefit matrix
| SA benefit | What it grants | Buyer value |
|---|---|---|
| Free passive secondaries | Up to 2 passive replicas per primary (HA/DR/backup) | High |
| License Mobility | Reassign across servers <90 days; move to hosters | High (virtualized estates) |
| Unlimited Virtualization | Unlimited SQL VMs on Enterprise-per-host | High (dense clusters) |
| Azure Hybrid Benefit | Reuse licenses in Azure (~55% Azure saving) | High if cloud-bound |
| Version upgrade rights | Free move to SQL 2025+ during term | Medium |
SA is compelling for Enterprise deployments, HA/DR estates, virtualized or mobile workloads, and anyone with a cloud roadmap — the passive-server and AHB rights alone often exceed the premium. It is weak value for a static single physical Standard server with no failover and no cloud plans. The critical catch: most of these rights evaporate the moment SA lapses. If it expires, your free passive replicas, mobility rights and Azure Hybrid Benefit all become non-compliant. Treat SA as an ongoing commitment, right-sized per workload.
Two mechanisms avoid buying perpetual licenses outright. Azure Hybrid Benefit (AHB): if you hold SQL core licenses with active SA, apply them to Azure SQL instead of paying full pay-as-you-go — Microsoft positions this as up to ~55 percent savings versus license-included pricing. Pay-as-you-go via Azure Arc: since SQL 2022 you can run SQL on-premises or in any cloud and pay hourly — Standard at $73 per core per month ($0.100/hr) and Enterprise at $274 per core per month ($0.375/hr) — billed to your Azure subscription.
PAYG is genuinely useful for short-lived, seasonal, dev/test or bursty workloads where a perpetual license would sit idle. But do the arithmetic: Enterprise PAYG at ~$274 per core per month reaches the ~$7,562 per-core perpetual list price in roughly 27 to 28 months, so steady production is usually cheaper to own. AHB is close to a free lunch if you already carry SA — elect it on every eligible Azure SQL resource, because it is opt-in and frequently left unchecked, silently doubling the Azure bill.
The rule that reshaped the landscape: as of the November 2019 update (carried into SQL 2022), free passive/failover rights require active Software Assurance or a subscription. Before that a passive secondary was effectively free; now it is an SA-gated benefit. With SA, each licensed primary grants up to two free passive secondaries covering the three sanctioned roles — high-availability failover, disaster recovery and backup. The secondary must be truly passive: it cannot serve reads, run reports, back up other databases, or do any active work, and its core count must match the primary. Since SQL 2019 a DR replica may sit in Azure under this benefit, but an HA replica in Azure must be fully licensed.
Two failure modes follow. First, Always On or a failover cluster without SA makes every secondary a fully licensable, chargeable server — a common, expensive audit finding. Second, the "truly passive" test is strict: the instant a DBA points reporting or read-only traffic at a secondary, that server loses its free status and must be fully licensed. Confirm SA is attached wherever you rely on free secondaries, and police read-intent routing and offloaded backups, because a well-meaning performance tweak can create a six-figure compliance gap. (SQL Server 2025 reached general availability on 18 November 2025 with no change to these models or list prices, so everything here still applies.)
White Paper · Microsoft
SQL Server 2022 Core Licensing (2026)
The per-core vs Server+CAL breakeven, current list prices, virtualization, and the Software Assurance benefits that decide your final bill. Read it free.
No — SQL Server 2022 counts every physical core as 1.0, so the old core-factor discount (for example 0.75 for certain AMD chips) no longer exists; reject any quote that applies one. You license all physical cores, with a minimum of four core licenses per instance, sold in 2-core packs.
Only if you have active Software Assurance — with SA, each licensed primary includes up to two free, truly-passive secondaries for HA, DR or backup; without SA, every secondary must be fully licensed. The replica must do no active work beyond receiving data, or it loses its free status.
SQL Server 2022 is licensed either per core or by Server plus CAL. Per core suits workloads with many or unknown users, while Server plus CAL suits small, countable user populations. Enterprise Edition is per core only, and Standard supports both models.
Per core licensing requires a minimum of four cores per physical processor or virtual machine, and licenses are sold in two core packs. Even a two core virtual machine must be licensed for the four core minimum.
Enterprise Edition costs roughly three to four times Standard per core and adds advanced availability groups, unlimited virtualization with Software Assurance, and higher scalability. Standard meets the needs of most general workloads at a far lower per core price.
Yes. A passive failover replica is only free of license cost when the primary carries active Software Assurance. Without Software Assurance, the passive replica must be fully licensed, which often adds twenty to forty percent to the bill.
Software Assurance enables License Mobility across servers, free passive failover rights, version upgrade rights, and the Azure Hybrid Benefit. For estates that move workloads or use Azure, those rights frequently justify the Software Assurance cost.
Yes. SQL Server 2022 supports pay as you go billing per core through Azure Arc, which turns the license into an hourly operating cost. This suits variable or short lived workloads better than a perpetual per core purchase.
On a virtual machine you license the assigned virtual cores, subject to the four core minimum. Alternatively, licensing all physical cores on the host with Enterprise Edition and Software Assurance grants unlimited virtualization on that host.
Yes, SQL Server Express is free but capped on database size, memory, and CPU use. It suits small applications and development, but production workloads usually outgrow its limits and need Standard or Enterprise Edition.
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.
SQL Server cost is decided before you install anything. Pick the edition for the workload, not the org, license replicas correctly, and the per core price stops being the problem.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on Microsoft licensing moves, EA and CSP mechanics, M365 and Azure SKU traps, and the buyer side levers we run in client engagements. No noise.
