فا
MSLicenseHub
database · reference
🗄️

SQL Server 2022

SQL Server 2022 — Azure-connected hybrid features, per-core and Server+CAL licensing, Standard vs Enterprise vs Developer.

SQL SERVER 2022
On this page

Editions · channels · activation · audit notes · FAQs

Editions covered
5
Edition matrix with feature differences and the right audience.
In-depth sections
6
Channels, activation, audit, modern management & more.
FAQs answered
6
Common questions buyers and IT admins ask before purchase.
Words of reference
0.7k
Plain-English, no vendor agenda, updated to current Product Terms.
Edition matrix

Pick the right edition

Each edition targets a specific scale and feature set. Match the workload, not the price tag.

Edition 1
Standard

Per-core or Server+CAL. 24-core / 128 GB caps. Basic AGs, two-node failover.

Edition 2
Enterprise

Per-core only. Unlimited cores, full AGs, online operations, advanced security.

Edition 3
Developer

Free. Functionally identical to Enterprise. Dev/test only — never production.

Edition 4
Express

Free engine for embedded scenarios. 10 GB database size cap.

Edition 5
Web

SPLA-only. Outward-facing public web workloads at hosting providers.

Side-by-side

Edition comparison

Heuristic capability matrix derived from each edition's intended use. For binding commitments, always confirm against the current Product Terms.

CapabilityStandardEnterpriseDeveloperExpress
Target audienceGeneralEnterpriseDeveloperGeneral
Domain / Entra join
Virtualisation rights
Advanced security
Centralised management
Volume Licensing path
Deep dive

SQL Server 2022 — what to actually know

SQL Server 2022 is the predecessor LTSC release to SQL Server 2025, with mainstream support through 11 January 2028 and extended support through 11 January 2033. Its headline themes are Azure integration (linked Azure Synapse Link for SQL, near-real-time analytics without ETL, managed disaster recovery through Azure SQL Managed Instance link, Azure Arc-enabled SQL Server for billing and inventory), security (Always Encrypted with secure enclaves, ledger tables for tamper evidence), and intelligent query processing improvements. For estates that standardised on SQL 2022 in the last three years, there is no compliance pressure to move to 2025; for greenfield deployments, 2025 is the default but 2022 remains fully supported and is sometimes preferred for application-vendor compatibility reasons.

01

Editions and where each one fits

Standard is the workhorse SKU for departmental and mid-tier production workloads — up to 24 cores, 128 GB buffer pool, two-node failover clustering, Basic Availability Groups, transparent data encryption, columnstore indexes (with feature caps versus Enterprise). Enterprise removes the caps: unlimited cores within the host, unlimited memory, full Availability Groups, online operations, partition switching, advanced compression, In-Memory OLTP at scale, advanced security features. Developer is functionally identical to Enterprise but licensed for development and test only — free, included with Visual Studio subscriptions, never permissible in production. Express is the free engine for small embedded scenarios. Web is sold only through SPLA hosters for outward-facing web workloads.

02

Per-core licensing — the rules that always trip teams up

SQL Server per-core licensing applies to every physical core on the host running SQL, sold in 2-core packs with a four-core minimum per processor. Hyperthreaded logical cores do not change the count. When SQL runs in a VM, you can license either the entire host (covering all VMs running SQL up to the unlimited virtualisation rights of Enterprise with SA) or just the VM's allocated vCPUs (minimum four). Mobility rights under Software Assurance allow SQL workloads to move between licensed hosts more frequently than the default 90-day rule. Per-core is the dominant model for production today; Server + CAL is permitted for Standard and Developer where every connected user or device can be enumerated, but rarely cheaper.

03

Server + CAL licensing

Standard with Server + CAL is sold as one server licence per running OSE plus a Client Access Licence per user or device that connects. CALs are version-tied: a SQL 2022 CAL covers earlier versions on the same connection (downgrade rights) but not later ones (upgrade requires new CALs or Software Assurance). Server + CAL only makes financial sense when the user or device count is small and stable; the moment a workload sees web traffic, anonymous connections, indirect users via a middle tier, or BI tools talking to the database on behalf of unknown end users, per-core becomes the safer and almost always cheaper model.

04

Hybrid Azure features unique to 2022 onward

Azure Synapse Link for SQL streams change-feed data from SQL Server 2022 to a Synapse dedicated SQL pool in near-real-time, enabling analytics without traditional ETL. The Azure SQL Managed Instance link replicates from on-prem SQL 2022 to a managed instance in Azure for disaster recovery, with read scale-out on the secondary. Azure Arc-enabled SQL Server registers on-prem instances with Azure for centralised inventory, Defender for SQL, Backup to Azure, and pay-as-you-go licensing on top of existing SQL Software Assurance. None of these features require migration of the production workload to Azure — they extend on-prem SQL with cloud-side capabilities.

05

Security: Always Encrypted with secure enclaves, ledger

Always Encrypted with secure enclaves (added in 2019, expanded in 2022) supports rich queries — range comparisons, sort, LIKE — on encrypted data by performing those operations inside a hardware-backed enclave, without exposing plaintext to the database engine. Ledger tables (introduced in 2022) provide blockchain-style append-only history with cryptographically verifiable proof of integrity, intended for regulatory and audit workloads. Both features are Enterprise-only in their full form; Standard supports baseline Always Encrypted without enclave operations.

06

Upgrade paths and the 2025 question

In-place upgrade from SQL 2019 or 2017 to SQL 2022 is supported. For SQL 2014 / 2016 estates, the standard guidance is to migrate to 2022 or 2025 (depending on application-vendor support matrix) rather than chain in-place upgrades. SQL 2025 added vector search, T-SQL JSON improvements, Microsoft Fabric mirroring and updates to intelligent query processing — meaningful for workloads that target those features, optional for the rest. The Microsoft licensing terms are unchanged between 2022 and 2025, so the migration cost is purely the operational testing and cutover, not the licence.

By channel

Where to buy this product

Relative fit of each licensing channel for typical buyers of this product. Calibrate against your own scale and renewal strategy.

Channel fit (typical buyer)
Retail / FPP1
Volume Licensing10
CSP / Azure8
Retail / FPPIndividuals & small teams

Boxed or ESD keys, transferable, registered to a Microsoft account.

Volume LicensingMid-market & enterprise

MAK / KMS activation, centralized VLSC, optional Software Assurance.

CSP / Microsoft 365Subscription, per user

Monthly / annual seats, managed through partner or admin center.

OEM is not a buying channel for end users. OEM keys are supplied pre-installed by hardware manufacturers and are not sold standalone — choose Retail, Volume or CSP instead.
Support timeline

Lifecycle phases to plan against

SQL Server is the most expensive product Microsoft sells per core. Edition, core count and licensing model (per-core vs Server+CAL) have life-changing cost implications — model them before you buy.

Phase 1
General availability
Launch

Standard, Enterprise and Developer editions release simultaneously. Developer is free for non-production.

Phase 2
Mainstream support
5 years

Cumulative updates roughly every two months, plus security fixes. New feature work lands here.

Phase 3
Extended support
Years 5–10

Security-only servicing. No new TLS ciphers, no new features. SA required for non-security hotfixes.

Phase 4
ESU
Years 10–13

Up to 3 years of paid Extended Security Updates, or free ESU when the workload is moved to Azure SQL or an Azure VM.

Procurement checklist

Do this, not that

The small set of decisions that determine whether you overpay, fail an audit, or land in the right place.

DO

License every physical core on every server that runs SQL, with the 4-core-per-instance minimum and 2-pack increments.

DON'T

License only one VM's worth of cores when the underlying host can re-schedule the VM to any other host — that is unlicensed mobility.

DO

Use Developer Edition for every non-production environment — it is feature-equivalent to Enterprise and free.

DON'T

Run real workloads on Express past the 10 GB / 1 GB-RAM / single-socket limits — it silently caps and corrupts capacity planning.

DO

Document HA topology: passive secondaries are free under SA, active secondaries (read replicas, ETL) are not.

DON'T

Assume Always On replicas are free — only one passive secondary per primary is included, and only with active SA.

DO

Consider Azure SQL Managed Instance or Azure SQL Database for new workloads — licensing collapses into the service cost.

DON'T

Buy Enterprise cores for a workload that fits comfortably in Standard — the price gap is large and Standard now covers most mid-market needs.

Typical deployments

How buyers actually use SQL Server 2022

Three reference deployments — find the closest match and adapt rather than starting from zero.

Scenario 1
Line-of-business ERP

Standard per-core on the active node, passive HA secondary covered by SA, regular backups to Azure Blob. Enterprise only if the ERP genuinely needs partitioning or in-memory OLTP.

Scenario 2
Data warehouse / BI

Enterprise per-core for columnstore at scale and advanced security. Consider Microsoft Fabric or Azure Synapse for greenfield analytics rather than scaling SQL Server vertically.

Scenario 3
ISV embedding SQL

Either bundle Express (with its caps) for free distribution, or buy SQL through the ISV royalty programme; never silently ship Developer Edition in a commercial product.

Cost optimisation

Where the savings actually live

None of these are tricks — they are the same levers Microsoft's own licensing specialists pull on every renewal.

💰
Standard wins for most mid-market apps

Standard covers 128 GB of buffer pool memory and most BI features. Reserve Enterprise for in-memory OLTP, advanced security, transparent data encryption at scale, or large data-warehouse workloads.

📊
Free passive secondary

With active SA, one passive HA replica per licensed primary is free. Plan your Always On topology to take advantage of this before adding paid secondaries.

🎯
Azure SQL for elastic workloads

Variable workloads (dev/test, reporting bursts, multi-tenant SaaS) collapse total cost in Azure SQL serverless or elastic pools versus statically licensed cores.

Counterfeit & risk

Red flags when buying second-hand

These four signals show up in every counterfeit-licence case we have seen. If any of them is present, walk away — no discount makes it worthwhile.

01
Standalone OEM key sold below market

OEM keys are distributed only pre-installed on hardware and stay bound to that device for life. A separately sold OEM key is almost certainly leaked, harvested from scrapped hardware, or fully counterfeit.

02
Lifetime key with no invoice or VLSC record

Microsoft entitlement always leaves a paper trail — a Volume Licensing Service Center record, a CSP invoice, a sealed Retail box with a COA, or a Microsoft Store order. No proof = no defence in an audit.

03
Key works once, then 'not genuine' after the next cumulative update

Classic symptom of a MAK key that has exceeded its activation pool, or a KMS key being abused outside its volume programme. Microsoft revokes these centrally; the activation grace period is short.

04
Seller refuses to put the entitlement in your tenant

Legitimate CSPs and LARs transfer the licence into your Microsoft 365 / Azure / VLSC tenant under your domain. If the seller insists on activating 'for you' on their account, you do not own anything.

Acronyms

Licensing terms used on this page

Quick definitions — the full glossary lives at /en/glossary if you need to dig deeper.

CSP

Cloud Solution Provider — Microsoft's primary indirect channel for subscriptions and cloud services.

VLSC

Volume Licensing Service Center — the portal where Volume Licensing keys, agreements and downloads live.

MAK

Multiple Activation Key — a Volume Licensing key with a finite activation count, used for isolated machines.

KMS

Key Management Service — an on-premises activation host that activates clients on a 180-day re-check cycle.

EA

Enterprise Agreement — Microsoft's largest commitment-based volume contract, typically a 3-year term with annual true-ups.

SA

Software Assurance — the upgrade-and-benefits add-on to Volume Licensing; required for new version rights and several mobility scenarios.

Browse the full glossary →
FAQ

Frequently asked questions

Per-core or Server+CAL — which?+
Default to per-core for production. Server+CAL only when every connecting user or device can be enumerated and that number is small and stable.
Do hyperthreads count?+
No. Per-core licensing is based on physical cores. Hyperthreaded logical CPUs do not change the licence count.
Is Developer Edition really free?+
Yes — free for use in development and test environments. It is identical in capability to Enterprise but licensed solely for non-production use. Auditors do check this.
Can SQL 2022 talk to Azure?+
Yes — Synapse Link for SQL, Managed Instance link for DR, Azure Arc for inventory and Defender for SQL all light up on 2022 and later.
Where can I legitimately buy a license?+
Through Microsoft's Retail channel, an authorised Cloud Solution Provider (CSP), or a Volume Licensing partner (MPSA, Enterprise Agreement, Open Value, Server & Cloud Enrollment). OEM keys are distributed only pre-installed by hardware manufacturers and stay bound to that device for life — they are not sold to end users as standalone products. Anyone offering a 'cheap OEM key' as a standalone download is, by definition, operating outside Microsoft's distribution terms.
What gets checked in a Microsoft licensing audit?+
Auditors map every installed copy to a proof of purchase (VLSC record, CSP invoice, sealed Retail FPP), verify edition alignment (features used must match the licensed edition), and confirm CAL counts cover the maximum number of authenticated users or devices during the audit window. Small variances usually resolve with a true-up; large gaps escalate to Software Asset Management engagements and back-billing at list price.
Related

Other products in this category