SQL Server 2016 died on 14 July 2026. If you are still on it, you are also on an X3 patch level that cannot leave it.
This is the trap that turns a database migration into an ERP programme, and it catches almost everyone who discovers it late.
Who it binds
- Any Sage X3 estate running Microsoft SQL Server 2016, in any environment — production, test, training or reporting.
- Extended Security Updates are available as a paid annual programme via Azure Arc for on-premise and multi-cloud, running three further years. They buy time; they do not fix the version floor.
What it actually demands
- Sage X3 releases prior to 2020 R3 (V12.0.23) support SQL Server 2016 and 2017 only. They cannot run SQL Server 2019 or 2022.
- Sage X3 2020 R3 (12.0.23) through 2023 R1 (12.0.33) run SQL Server 2019. From 2023 R1 (12.0.33), SQL Server 2022.
- Since Sage X3 2026 R1 (V12.0.39), Sage X3 does not support SQL Server 2016 at all.
- Patches from 2019 R5 (12.0.20) are cumulative, and the minimum prerequisite to apply them is 2019 R4 (12.0.19). Below that, the cumulative path is closed.
An estate on SQL Server 2016 is, by definition, on an X3 patch level below 12.0.23 — so the database cannot be moved without moving the ERP in the same project. A sixteen-plus patch-level jump is not a maintenance window. Priced and scheduled as a standalone database migration, it fails at the point where the new SQL version refuses the old X3 build, usually after the outage has been booked.
What it means for the estate
Establish the actual floor per environment before anything else. Sage publishes a support-status label per release, not a per-release calendar date, and the estate is frequently on a different patch level in test than in production.
The remediation is one project: X3 patch level, SQL Server and Windows Server move together. Windows Server 2016 reaches end of support on 12 January 2027, and Sage X3 2025 R1 (12.0.37) and above require Windows Server 2025 — so the operating system is the third leg of the same lift, not a follow-on.
Sequence it ahead of any compliance data build. Master data and transaction design landing on an estate that cannot take a patch gets built twice.
Caveat
Sage's own prerequisites page is internally inconsistent on when SQL Server 2016 support ended — the support matrix implies 12.0.22, a footnote implies 12.0.38. Establish the floor empirically for your estate rather than quoting the document.
Primary sources
Run the exposure check — three minutes, free, and it will tell you which of the other 11 dates catch you as well and in what order they have to be done. Sequencing is most of the cost on these programmes.