Back to blog

OSSeva Blog

Operations

SQL Server 2019 end of support: the dates, and when moving to PostgreSQL pays

Matt ReynoldsUpdated 7 min read

Dates checked on 20 October 2026 against endoflife.date and Microsoft's lifecycle pages.

Leaving SQL Server?

Migration to PostgreSQL, with 24/7 support afterwards on infrastructure you control. OSSeva does not support or patch SQL Server itself.

SQL Server to PostgreSQL migration →

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

SQL Server 2019 end of life: the short answer

SQL Server 2019 end of life is 8 January 2030, when Microsoft ends extended support and stops shipping security updates. Mainstream support already ended on 28 February 2025, so 2019 receives security updates only. The dates on this page were checked against endoflife.date and Microsoft's lifecycle pages on 20 October 2026 and re-read on 17 November 2026. If the end date sits next to a licence renewal, the choice is to upgrade within SQL Server or move to PostgreSQL; send your work email in the form above and an OSSeva engineer replies within 1 business day.

Planning past the end date? SQL Server end of life sets out each version's dates and ESU terms next to the migration to PostgreSQL option. On Windows Server 2016? Its extended support ends on 12 January 2027, a different date: Windows Server 2016 end of support lists what each workload on it is running to.

SQL Server 2016, 2017 and 2019 support dates

VersionMainstream support endedEnd of extended supportExtended Security Updates
SQL Server 2016 (SP3)13 July 202114 July 2026 (passed)Paid, to 17 July 2029
SQL Server 201711 October 202212 October 2027None announced
SQL Server 201928 February 20258 January 2030None announced
SQL Server 202211 January 202811 January 2033Not applicable yet
SQL Server 20256 January 20316 January 2036Not applicable yet

Checked 20 October 2026 against the SQL Server dataset at endoflife.date and Microsoft's lifecycle pages; Microsoft publishes its dates in Pacific Time. For the 2016 mainstream date endoflife.date lists 14 July 2026, so we use Microsoft's own lifecycle page, which gives 13 July 2021. SQL Server 2019 was released on 4 November 2019, and the lifecycle covers all editions on Windows and Linux. Microsoft's ESU documentation lists SQL Server 2014 and 2016 only, so no Extended Security Updates programme exists for 2017 or 2019 today.

For ESU prices on the versions that already have them, SQL Server ESU cost against a migration to PostgreSQL sets the figures beside the PostgreSQL alternative.

Searching for "SQL 2016 end of life" or "SQL Server 2017 EOL"? The table has both: 2016 left extended support on 14 July 2026, and 2017 follows on 12 October 2027.

What happens after extended support ends

Microsoft's lifecycle gives each version five years of mainstream support, with functional, performance, scalability and security updates, then five years of extended support, with security updates only. Since 28 February 2025, a SQL Server 2019 bug that is not a security issue no longer qualifies for a public fix. SQL Server Big Data Clusters, which shipped with 2019, were retired the same day.

On 8 January 2030, SQL Server 2019 end of support means:

  • Security updates stop, unless Microsoft announces an ESU programme for 2019, which it had not done at the check date.
  • Microsoft product support for the version ends.
  • Instances still on 2019 become audit findings under most control frameworks.
  • Nothing stops on the day. The databases keep running, with no new fixes.

Upgrades and migrations across a large estate need testing time, so the date to plan around is earlier than January 2030.

Renew, pay for ESU, or move

The routes below apply to 2019 the same way as to the other versions; SQL Server end of support options covers each in turn.

RouteWhat you getWhat it costs you
Upgrade to SQL Server 2022 or 2025A supported version; both accept an upgrade from 2019, and 2025 has the longer runwayNew licences or a Software Assurance renewal on Microsoft's terms, plus application testing
Extended Security UpdatesNothing for 2019 today. For 2016 they are Critical fixes only, for up to three years, and Microsoft calls them a temporary bridgeA paid subscription; there is no ESU to buy for 2019 until Microsoft announces one
Azure SQL Managed Instance or DatabaseA managed service that Microsoft says never reaches end of supportYour databases move onto Microsoft's cloud service and its terms
Move to PostgreSQLAn open source database with no per-core licence, on infrastructure you controlA migration project, sized to your estate, then a PostgreSQL support subscription priced per cluster

How to compare a SQL Server renewal with a move

Microsoft licenses SQL Server Standard and Enterprise per core, sold in two-core packs with a minimum of four core licences per processor, and Standard can also be licensed per server plus client access licences. Use the price in your own agreement, not list price, and work through four steps:

  1. Count the licensed cores on every SQL Server 2019 instance, including disaster recovery and test servers that are licensed.
  2. Multiply by the per-core price and any Software Assurance or subscription charge in your agreement, for the years you would otherwise renew.
  3. List what a move adds: assessment, T-SQL conversion, application testing, a parallel run and cutover, and PostgreSQL support afterwards.
  4. Compare the two. A move pays when the renewal is large, the applications are yours to change, and the cutover can fit a downtime window you can accept.

The database support cost calculator takes your own inputs for the support side. OSSeva does not publish prices; support is priced per cluster, and a discovery call gives you the quote to put beside your renewal.

What a move to PostgreSQL involves

OSSeva does not support or patch SQL Server. For a version upgrade, staying with Microsoft is usually the simpler path. For applications you own, SQL Server to PostgreSQL migration, with support afterwards runs six steps: an assessment of every database, T-SQL object and client that connects, schema and T-SQL conversion, rehearsed data loads with validation, a parallel run, a cutover with a rollback plan, and PostgreSQL support from the day you cut over.

The size of the work is set by factors you can count, not a standard duration: the number and size of schemas, the volume of T-SQL in stored procedures and triggers, the number of applications, SSIS packages and reports that connect, and the downtime window you can accept. Two paths exist for the code: convert to native PostgreSQL, or keep much of the T-SQL on Babelfish. The SQL Server to PostgreSQL migration guide compares a native rewrite, pgloader and Babelfish.

After cutover, OSSeva Assure includes 24/7 reactive support, and OSSeva Operate adds managed operations with a 15-minute P1 incident response. Pick the tier at the quote stage.

Frequently asked questions

When is SQL Server 2019 end of life?

8 January 2030, the end of extended support. Mainstream support ended on 28 February 2025.

Is server 2019 EOL?

Not yet. SQL Server 2019 is in extended support, which delivers security updates only, and that ends on 8 January 2030. Windows Server 2019 has its own lifecycle, separate from SQL Server's.

Is SQL 2014 EOL?

Yes. SQL Server 2014 left extended support on 9 July 2024. Extended Security Updates for it run to 12 July 2027.

When is SQL Server 2016 end of life, and 2017?

SQL Server 2016 reached end of extended support on 14 July 2026, with paid ESUs to 17 July 2029. SQL Server 2017 follows on 12 October 2027. Our 2016 and 2017 posts cover each.

What is the SQL Server 2019 end of service date?

Microsoft uses "end of support". For SQL Server 2019 that is 8 January 2030, after which no further updates ship.

Will there be ESUs for SQL Server 2019?

Microsoft has announced none. Its ESU documentation, checked on 20 October 2026, lists SQL Server 2014 and 2016 only.

What is the price of SQL Server Standard Edition?

Microsoft sets it, per core or per server plus client access licences, and it varies by agreement and changes between releases, so this page quotes no figure. Check Microsoft's SQL Server pricing page or your reseller, and use the number from your own agreement when you compare a renewal with a move.

Which SQL Server version should we upgrade 2019 to?

SQL Server 2025 has the longest window, with extended support to 6 January 2036. SQL Server 2022 is the other supported target, with mainstream support to 11 January 2028.

Tags

SQL ServerSQL Server 2019End of SupportPostgreSQL

Get a quote

Leaving SQL Server? Send your work email.

An OSSeva engineer replies within 1 business day with an assessment plan and a quote, priced per cluster.

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

Prefer to talk or read more first?

Book a call