SQL Server 2019 vs 2025: Features, Licensing and Pricing Comparison
SQL Server 2019 left mainstream support on February 28, 2025, earlier this year. Extended support, security fixes only, runs to January 8, 2030. That is a longer runway than Windows Server 2019 gets, and it is a different kind of comparison: on Windows Server, the licensing model did not move at all between the two versions. On SQL Server, two things actually did.
What did not move
| Rule | 2019 | 2025 |
|---|---|---|
| Enterprise edition | Per Core only | Same |
| Standard edition | Per Core or Server + CAL | Same |
| Per-core minimum | 4 core licences per physical processor or per VM | Same |
| Core SKUs sold as | 2-core packs | Same |
| Licensing a VM | Physical cores, or by VM with Software Assurance or a subscription | Same |
| Azure Hybrid Benefit | Same core-to-vCore math as Windows Server | Same |
Do not carry the 8-core, 16-per-server floor over from a Windows Server comparison. SQL Server's minimum is four core licences per physical processor, on 2019 and on 2025 alike; the two products' floors have never matched, and nothing in this release changed that.
What did move
- Standard edition's ceiling is higher. 2019 caps Standard at the lesser of four sockets or 24 physical cores, and 128 GB of buffer pool memory. 2025 raises both: 32 cores and 256 GB. An estate that outgrew Standard on 2019 and was pricing an Enterprise upgrade for capacity alone should re-run that number against 2025's ceiling before buying the more expensive edition.
- Power BI Report Server's licence changed, on 2025 only. On 2019 and every version up to 2022, Power BI Report Server use rights come only with Enterprise edition core licences under active Software Assurance. On 2025, those rights ship with Standard edition too, and without requiring Software Assurance. This does not apply retroactively to a 2019 or 2022 licence; it is a 2025-only entitlement, and it lands alongside Microsoft's move away from classic SQL Server Reporting Services toward Power BI Report Server as the reporting engine going forward.
Both are real entitlement changes, not marketing language, and both cut cost in the same direction: a workload that needed Enterprise on 2019 purely for compute headroom or for Power BI Report Server may not need it on 2025. Verify against your own core count and reporting footprint before assuming either applies; capacity limits and the Power BI Report Server right are edition and version-specific, not something a general estimate should extrapolate from.
What is new in the engine, separate from the licence
- Native vector data types and in-database AI functions (
AI_GENERATE_EMBEDDINGS,VECTOR_SEARCH), backed by a DiskANN index, none of which exist on 2019. - Fabric Mirroring: near-real-time replication into Microsoft Fabric without a separate ETL pipeline, new to 2025.
- Native regular expressions in T-SQL, REST endpoints, GraphQL, and Entra ID authentication extended down to Express edition.
None of these change a core count. They are reasons to move that sit next to the licensing reasons, not inside them, the same separation that matters on the Windows Server side of an estate too.
The upgrade path
SQL Server's supported upgrade matrix is wider than Windows Server's. A direct in-place upgrade to 2025 is supported from 2019, and from every version back to 2016 SP3 and 2014 SP3. There is no forced stop at one version back the way a clustered Windows Server host has to roll through 2022 first; a 2019 SQL Server instance can go to 2025 directly, in place, without a stop in between. Cross-platform upgrades (32-bit to 64-bit, one OS platform to another) are still not supported, and no new features are added mid-upgrade; the instance lands on 2025 at its existing feature set, not with vector search or Fabric Mirroring switched on by default.
Do not invent a list price for either version here either. Per-core figures move by channel and agreement, Enterprise Agreement, MPSA, or a CSP subscription, and the only number that means anything is the one on the quote in front of you, for 2019 as much as for 2025.
What decides the real position either way is edition and core count against what is actually deployed and actually used, Standard versus Enterprise, physical versus per-VM, not a spreadsheet built from the version number alone. Microsoft Deployment Manager reads that from the estate's real Microsoft deployment data, on-premise and cloud, so a mixed 2019-and-2025 SQL Server estate, which is what most migrations run for a year or more, gets priced against what is running today, not an assumption that the cutover already finished.
The same pattern, a fixed edition ceiling that decides whether the cheaper tier still covers the workload, is the same question Oracle's SE2-to-Enterprise line draws: know the ceiling before the workload grows into a licence you did not plan to buy.
Checklist
- Every SQL Server 2019 host's extended-support date checked against January 8, 2030.
- Any Enterprise purchase justified by compute headroom alone re-priced against 2025 Standard's 32-core, 256 GB ceiling first.
- Power BI Report Server usage checked against which SQL Server version actually licenses it: Enterprise-with-SA on 2019 and 2022, Standard included on 2025.
- Per-core counts re-verified per instance, physical or per-VM, not assumed unchanged just because the minimum itself did not move.
