SQL Server versions and end-of-support dates

SQL Server versions, release dates and support end dates

Microsoft supports each SQL Server version for ten years: five of mainstream support and five of extended support, which carries security updates only. Extended Security Updates (ESUs) are a paid third stage that Microsoft has offered for SQL Server 2012, 2014 and 2016. Status is as of 22 October 2026.

Sources: Microsoft Lifecycle pages for each SQL Server version and Microsoft's SQL Server ESU FAQ, cross-checked against endoflife.date. Microsoft lists SQL Server 2014 ESUs ending on 12 July 2027 on its Lifecycle page and Windows Server ESU page, and on 8 July 2027 in the ESU FAQ; this page uses 12 July 2027. Microsoft has published no ESU programme for SQL Server 2017 or later.

Latest SQL Server update for each version

The build number in @@VERSION shows whether an instance has the newest update for its version. These are the latest builds listed on endoflife.date for each version on 22 October 2026.

How to check your SQL Server version

Connect with SQL Server Management Studio, Azure Data Studio or sqlcmd and run the query below. The first line of the result names the product, for example Microsoft SQL Server 2019, and shows the build number, such as 15.0.4xxx.x. The first two numbers of the build give the version: 17.0 is SQL Server 2025, 16.0 is 2022, 15.0 is 2019, 14.0 is 2017, 13.0 is 2016, 12.0 is 2014 and 11.0 is 2012.

The same query works on Windows and on Linux. In Management Studio you can also right-click the server in Object Explorer and open Properties, which shows the product version and edition. To tell which update an instance has, compare its full build number with the latest-build table above.

SELECT @@VERSION;

SELECT
  SERVERPROPERTY('ProductVersion')     AS product_version,
  SERVERPROPERTY('ProductLevel')       AS product_level,
  SERVERPROPERTY('ProductUpdateLevel') AS update_level,
  SERVERPROPERTY('Edition')            AS edition;

ProductLevel shows the service pack or RTM, and ProductUpdateLevel shows the cumulative update where one is installed. Edition matters for support: Microsoft offers ESUs for the Enterprise and Standard editions of SQL Server 2014 and 2016 only, not for Express, Web or Developer.

What end of support means for SQL Server, and what ESUs cost

Mainstream support ends first: after that date Microsoft ships security updates only, and a performance or functional bug gets no public fix. When extended support ends, Microsoft ships no updates for that version at all, and it will not take a support ticket for it. The databases keep running.

Microsoft sells Extended Security Updates for up to three years after the extended end date, for SQL Server 2014 and 2016 only. ESUs cover Critical security updates, released only when the Microsoft Security Response Center rates a vulnerability Critical. Microsoft's published pricing is built from the rules below. Per-core prices are on Microsoft's Azure Arc pricing page, which this page does not copy because they change.

Sources: Microsoft Learn, "What are Extended Security Updates?", "Extended Security Updates FAQ" and "Extended Security Updates enabled by Azure Arc", read 22 October 2026.

Upgrade SQL Server or move to PostgreSQL

Most teams on SQL Server 2014 to 2017 have three routes. Upgrade to SQL Server 2022 or 2025, which restarts the support clock on Microsoft's licensing. Move the database to Azure SQL Managed Instance or Azure SQL Database, which Microsoft says never reach end of support. Or move the application to another database.

OSSeva does not support or patch SQL Server. If the application is a candidate to leave SQL Server, OSSeva assesses it, converts the schema and T-SQL, moves the data and then supports the PostgreSQL clusters, on infrastructure you control. Where an upgrade is the better answer, the assessment says so. Each route, version by version, is set out on the SQL Server end-of-life options page.