Back to blog

OSSeva Blog

Operations

SQL Server 2016 on Windows Server 2016: Two Deadlines, One Plan

5 min read

The short answer

A server running SQL Server 2016 on Windows Server 2016 has two separate end dates: SQL Server 2016 reached end of support on 14 July 2026, and Windows Server 2016 reaches it on 12 January 2027. Fixing one does not fix the other, so plan them together. OSSeva does not patch Windows Server or SQL Server; the SQL side of the plan is the choice set out in SQL Server end of support options.

Running open source in production? OSSeva patches and supports it, end-of-life versions included.

The two clocks

ProductExtended support endsPaid Extended Security Updates
SQL Server 201614 July 2026 (passed)Three years, to 17 July 2029; Critical updates only
Windows Server 201612 January 2027Microsoft lists three years, to 8 January 2030

Dates read on Microsoft's Lifecycle pages and end-of-support lists and on endoflife.date on 17 November 2026; the Windows Server ESU years are as set out in our Windows Server 2016 end of support post. Microsoft's ESU FAQ describes ESUs as a temporary bridge, and a late SQL Server enrolment is back-billed to the end date.

What are the ways to handle both?

RouteWhat it doesWatch for
Rebuild on a new serverInstall a current Windows Server and a current SQL Server together and move the databases acrossSQL Server 2025 accepts an upgrade from 2016 SP3 or later; check Microsoft's requirements for the Windows Server version you choose
Bridge both with ESUsKeep the server as is and buy ESUs for each productTwo paid programmes, each a temporary bridge; the Windows ESU purchase route was still being finalised in Microsoft's own post
Move the database off SQL ServerMigrate the database to PostgreSQL on infrastructure you control, which removes the SQL Server clock and its licenceA migration with T-SQL rewrites; the Windows Server date still applies to anything else on the box

Microsoft's end-of-support guidance notes that an unsupported Windows Server version also needs an OS upgrade when you stay on SQL Server. Order matters: decide the database route first, because it decides whether the new server needs SQL Server at all.

Where OSSeva fits

OSSeva covers one route: SQL Server to PostgreSQL migration, with PostgreSQL support from cutover, priced per cluster. It does not supply Windows ESUs, patch Windows Server or patch SQL Server. For the rest of the Windows estate, see Windows Server 2016 end of support, and for the SQL Server dates, SQL Server 2016 end of life.

Frequently asked questions

When does Windows Server 2016 reach end of support?

12 January 2027, according to Microsoft's end-of-support list for 2027.

Is SQL Server 2016 still supported?

Extended support ended on 14 July 2026. Only paid ESUs, to 17 July 2029 and Critical fixes only, remain.

Does upgrading Windows Server fix the SQL Server 2016 end date?

No. SQL Server has its own lifecycle; upgrading the operating system does not extend it.

Can I upgrade SQL Server 2016 straight to SQL Server 2025?

Yes, from SQL Server 2016 SP3 or later.

Tags

SQL ServerSQL Server 2016Windows Server 2016End of Support

Get a quote

Ready to get your open source under control?

Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call