فا
MSLicenseHub
database · reference
🗄️

SQL Server 2019

SQL Server 2019 — Big Data Clusters, intelligent query processing, per-core and Server+CAL licensing.

SQL SERVER 2019
On this page

Editions · channels · activation · audit notes · FAQs

Editions covered
4
Edition matrix with feature differences and the right audience.
In-depth sections
4
Channels, activation, audit, modern management & more.
FAQs answered
5
Common questions buyers and IT admins ask before purchase.
Words of reference
0.4k
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
SQL Server 2019 Enterprise

All features. Per-core licensing, two-core packs, minimum four cores per processor.

Edition 2
SQL Server 2019 Standard

24-core cap. Per-core or Server+CAL. Basic high availability.

Edition 3
SQL Server 2019 Web

Hosting-only SKU sold through SPLA.

Edition 4
SQL Server 2019 Developer / Express

Free editions. Developer is non-production; Express has a 10 GB database cap.

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.

CapabilitySQL Server 2019 EnterpriseSQL Server 2019 StandardSQL Server 2019 WebSQL Server 2019 Developer / Express
Target audienceEnterpriseGeneralGeneralDeveloper
Domain / Entra join————
Virtualisation rights————
Advanced security————
Centralised management————
Volume Licensing path✓———
Deep dive

SQL Server 2019 — what to actually know

SQL Server 2019 shipped in November 2019 and introduced Big Data Clusters (Kubernetes-hosted SQL + Spark + HDFS), intelligent query processing (adaptive joins, batch mode on rowstore, table variable deferred compilation), Always Encrypted with secure enclaves, accelerated database recovery, and UTF-8 collation support. It remains in mainstream support until 28 February 2025 and extended support until 8 January 2030 — still the most commonly deployed on-premises SQL Server release in the field today.

01

Editions and core feature matrix

Enterprise (unlimited cores, all features — Always On with multiple readable secondaries, online operations, in-memory OLTP without size cap, transparent data encryption, audit, advanced compression), Standard (24-core cap per instance, basic Always On with one synchronous secondary, transparent data encryption added in cumulative update 8 of 2019 SP — previously Enterprise-only), Web (low-cost hosting SKU for public-facing workloads), Developer (Enterprise feature set, non-production only, free), Express (10 GB database cap, free, redistributable).

02

Licensing models

Two licensing models: per-core (sold in two-core packs, minimum of four cores per physical processor) and Server+CAL (Standard only, one Server licence per instance plus a CAL for every user or device authenticating). Software Assurance is required for licence mobility to virtual machines that move between hosts, for failover rights, and for stepping into a newer version when one ships. Big Data Clusters were licensed under the same per-core model and were officially retired by Microsoft in 2025 — new deployments should use Azure Synapse or Microsoft Fabric instead.

03

Big Data Clusters and the deprecation note

Big Data Clusters (BDC) was SQL Server 2019's flagship feature: a Kubernetes-managed cluster combining a SQL Server instance, Apache Spark, HDFS and a scale-out compute pool. Microsoft announced retirement of BDC in February 2024, with extended support continuing until SQL Server 2019's own end of support in January 2030 — but no further investment. Customers running BDC should plan migration to Microsoft Fabric, Azure Synapse Analytics, or a third-party Spark distribution.

04

Support and migration

Mainstream support ended 28 February 2025; extended support through 8 January 2030. Customers running 2019 in production should plan an upgrade to SQL Server 2022 or 2025 before extended support ends. Side-by-side installation is supported on the same Windows Server, so a 2019 instance and a 2022 instance can coexist during migration testing.

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 2019

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

Is this product still supported by Microsoft?+
Mainstream support ended 28 February 2025; extended support 8 January 2030. After extended support ends, no security updates are released through public Windows Update and the only path to continued patches is the Extended Security Updates (ESU) programme where Microsoft offers it. Running an unsupported version in production is a documented audit and compliance risk.
Is Big Data Clusters still a viable platform?+
No — Microsoft has retired the feature and recommends Microsoft Fabric or Azure Synapse for new analytical workloads. Existing BDC deployments receive security patches through SQL Server 2019's end of support but no new functionality.
Can SQL Server 2019 Enterprise be licensed by Server+CAL?+
No — Enterprise edition is per-core only since SQL Server 2012. Server+CAL remains available for Standard.
Where can I legitimately buy a license?+
Through Microsoft's Retail channel (where the SKU is still sold), 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. For end-of-sale products, second-user (transferred) Volume Licensing through a documented chain of custody is the only legitimate secondary market.
What gets checked in a Microsoft licensing audit?+
Auditors map every installed copy to a proof of purchase (VLSC record, CSP invoice, sealed Retail packaging), verify edition alignment, and confirm CAL counts cover the maximum number of authenticated users or devices during the audit window. Older products are audited the same way as current ones — being out of mainstream support does not waive the licensing obligation.
Related

Other products in this category

🗄️
SQL Server 2025

SQL Server 2025 — editions, per-core vs Server+CAL, Azure-connected features and Software Assurance benefits.

Read reference →
🗄️
SQL Server 2022

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

Read reference →
🐧
SQL Server 2017

SQL Server 2017 — first SQL Server on Linux, adaptive query processing, graph data, Python machine learning services.

Read reference →