database · reference

🗄️

SQL Server 2019

Name: SQL Server 2019 licensing
Brand: Microsoft

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

Before licensing SQL Server 2019

SQL Server 2019 · licensing decision diagram, not a product screenshot

For SQL Server per-core licensing, check the four-core minimum per physical processor or individually licensed VM. Standard may use Server + CAL; multiplexing does not remove CAL requirements. Validate passive-replica and mobility rights separately.

Confirm against official Microsoft sources

Licensing terms and guides · Product lifecycle directory

Record the exact edition, version, quantity, agreement and support date. Obtain written confirmation of delivery, refund and support terms; a perpetual licence is not a lifetime support guarantee.

On this page

Editions covered

Edition matrix with feature differences and the right audience.

In-depth sections

Channels, activation, audit, modern management & more.

FAQs answered

Common questions buyers and IT admins ask before purchase.

Words of reference

0.4k

Edition and deployment guidance; verify current rights against official sources.

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

Compare the stated edition details. An omitted capability is not evidence that a feature is unavailable; verify the exact release in Microsoft's documentation.

Capability	SQL Server 2019 Enterprise	SQL Server 2019 Standard	SQL Server 2019 Web	SQL Server 2019 Developer / Express
Edition and licensing notes	All features. Per-core licensing, two-core packs, minimum four cores per processor.	24-core cap. Per-core or Server+CAL. Basic high availability.	Hosting-only SKU sold through SPLA.	Free editions. Developer is non-production; Express has a 10 GB database cap.

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. Mainstream support ended on 28 February 2025 and extended support (security updates only) runs until 8 January 2030 — it is still one of the most commonly deployed on-premises SQL Server releases.

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, which SQL Server 2019 added to Standard — 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).

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 retired by Microsoft on 28 February 2025 — new deployments should use Azure Synapse or Microsoft Fabric instead.

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 the retirement of BDC in February 2022 and retired it on 28 February 2025; it receives no further investment or support. Customers running BDC should plan migration to Microsoft Fabric, Azure Synapse Analytics, or a third-party Spark distribution.

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

Confirm that the exact SKU is available in the proposed channel and region. A channel name does not establish entitlement or guarantee a lower price.

Evidence to request

Exact product, edition, version and licence quantity.
Order, invoice and applicable agreement or subscription record.
Ownership in your organisation's account, where applicable.
Written reassignment, renewal and support conditions.

OEM is supplied only pre-installed by hardware manufacturers, never sold as a standalone licence.

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

Exact product

Identify

Record the release, edition and servicing channel of SQL Server 2019; family names alone do not establish support dates.

Phase 2

Official lifecycle

Verify

Look up the exact product in Microsoft's lifecycle directory. Fixed and Modern Lifecycle policies differ; not every release has extended support.

Phase 3

Deployment

Plan

Confirm supported operating systems, application dependencies and upgrade rights before deployment.

Phase 4

End of support

Migrate

A perpetual licence can remain valid after support ends, but it does not guarantee security updates. Check any ESU programme separately.

Purchase preparation

What to include in a SQL Server 2019 quote request

Edition and model: Exact version and edition; Per Core or eligible Server + CAL model.
Deployment: Physical processors and cores, or vCPUs per individually licensed VM.
Access: Users and devices, including indirect access when CALs apply.
Resilience: Active and passive replicas, HA/DR use and existing coverage.

These are planning inputs, not a licence calculation. Confirm the final quantity and use rights against the exact version and agreement.

Compare like-for-like quotations

Match product, edition, version, quantity and perpetual or subscription terms.
Confirm total cost, renewal conditions and the evidence of ownership supplied.
Obtain written delivery, refund and support conditions before payment.

Official product licensing guide

Request a quote

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.

License every physical core on every server that runs SQL, with the 4-core-per-physical-processor or individually licensed VM 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.

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

DON'T

Carry SQL Server 2022 Express limits into SQL Server 2025: verify the exact release matrix before sizing production workloads.

Document qualifying HA and disaster-recovery rights, locations and permitted passive maintenance activities under the applicable subscription or Software Assurance terms.

DON'T

Assume every replica is covered: application queries and active reporting can require separate licensing; validate each failover scenario.

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

Illustrative planning scenarios, not customer case studies. Check the exact product rights and deployment requirements.

Scenario 1

Line-of-business ERP

Standard per-core on the active node, passive HA secondary covered by SA, regular backups to Azure Blob. Choose the edition against the exact ERP requirements and release-specific feature limits.

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

Compare entitlement, deployment and renewal costs; savings depend on your workload and written quotation.

💰

Standard wins for most mid-market apps

Verify the edition limits for the exact SQL Server release. Features such as TDE, partitioning and in-memory OLTP are not universally Enterprise-only; compare official edition matrices before paying for Enterprise.

📊

Free passive secondary

Qualifying subscription or Software Assurance rights can cover passive HA and disaster-recovery deployments. Validate the allowed topology and activities before counting a replica as covered.

🎯

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 warning signs require further verification; activation alone cannot establish licence ownership.

⚠ 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 not an eligible standalone purchase; request documented rights through an appropriate channel.

⚠ 02

Lifetime key with no invoice or Microsoft 365 admin center volume licensing record

Request applicable order and agreement records, such as Microsoft Store purchases, CSP subscription records or volume licensing details in the Microsoft 365 admin center. Activation alone is not proof of entitlement.

⚠ 03

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

Activation failures can have several causes, including key eligibility, activation counts, connectivity and hardware changes. Check the error through official Microsoft guidance; it does not by itself prove counterfeiting.

⚠ 04

Seller refuses to put the entitlement in your tenant

For tenant-based subscriptions, confirm your organisation controls the tenant and can read its subscription records. Retail and on-premises entitlements use different records; not every licence is assigned through a tenant.

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.

Microsoft 365 admin center volume licensing

Volume licensing administration — agreements, keys and downloads are now managed in the Microsoft 365 admin center.

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.

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

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?+

Only with security updates. Mainstream support ended 28 February 2025; extended support (security updates only) continues until 8 January 2030. Plan the upgrade before that date — after it, the only path to patches is a paid Extended Security Updates (ESU) programme where Microsoft offers one.

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.

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 →