SQL Server Version Numbers

SQL Server Build and Version Number Reference

It’s a common troubleshooting step to check exactly which build of SQL Server you’re running against — the friendly “SQL Server 2016” style name doesn’t tell you the service pack or cumulative update level, and support articles usually reference the numeric build. Here’s a quick reference for the RTM and service pack build numbers from SQL Server 2008 R2 through 2016:

Version	Build
SQL Server 2008 R2 (Kilimanjaro)	10.50.1600.1
SQL Server 2008 R2 SP1	10.50.2500.0
SQL Server 2008 R2 SP2	10.50.4000.0
SQL Server 2012 (Denali)	11.0.2100.60
SQL Server 2012 SP1	11.0.3000.0
SQL Server 2012 SP2	11.0.5058.0
SQL Server 2012 SP3	11.0.6020.0
SQL Server 2014 (SQL14)	12.0.2000.8
SQL Server 2014 SP1	12.0.4100.1
SQL Server 2014 SP2	12.0.5000.0
SQL Server 2016 RTM	13.0.1601.5

Newer Releases (2017 Through 2025, Updated for 2026)

The same idea extends cleanly to every release since 2016 — each major version keeps its own build-number series, starting from its RTM:

Version	RTM Build
SQL Server 2017 RTM	14.0.1000.169
SQL Server 2019 RTM	15.0.2000.5
SQL Server 2022 RTM	16.0.1000.6
SQL Server 2025 RTM	17.0.1000.7

SQL Server 2025 reached general availability on 18 November 2025, making it the current release as of 2026. As with earlier versions, Microsoft has already shipped cumulative updates on top of the 2025 RTM baseline, so a freshly-patched 2025 instance will report a higher build than 17.0.1000.7 — check Microsoft’s own release-build tracking page for the exact CU-level build you’re seeing if you need to pin down patch currency precisely, rather than assuming RTM. To find your own instance’s exact build, run SELECT @@VERSION; in SQL Server Management Studio, or check the version number against the running list Microsoft maintains for each release, since new cumulative updates are published regularly and this table only covers major milestones rather than every CU.

Resources

• WQL
• our SQL & WQL query library