Release | RTM | Latest Update | ||||
---|---|---|---|---|---|---|
↓SQL Server 2019 Version: 15.0 Mainstream support end: 01 July 2025 Extended support end: 1 August 2030 | 15.0.2000.5 | CU14 – 15.0.4188.2 | ||||
↓SQL Server 2017 Version: 14.0 Mainstream support end: 11 October 2022 Extended support end: 12 October 2027 | 14.0.1000.169 | CU27 – 14.0.3421.10 | ||||
SQL Server Service Packs are discontinued starting from SQL Server 2017 – KB4041553 | ||||||
Release | RTM | SP1 | SP2 | SP3 | SP4 | Latest Update |
↓SQL Server 2016 Version: 13.0 Mainstream support end: 07 July 2021 Extended support end: 14 July 2026 | 13.00.1601.5 | 13.0.4001.0 | 13.0.5026.0 | 13.0.6300.2 | 13.0.6404.1 (hotfix for SP3) |
Release | RTM | SP1 | SP2 | SP3 | SP4 | Latest Update |
---|---|---|---|---|---|---|
↓SQL Server 2014 Version: 12.0 Mainstream support end: 9 July 2019 Extended support end: 9 July 2024 | 12.00.2000.8 | 12.0.4100.1 | 12.0.5000.0 | 12.0.6024.0 | 12.0.6433.1 (SP3 CU4 + Security Update) | |
↓SQL Server 2012 Version: 11.0 Mainstream support end: 11 July 2017 Extended support end: 12 July 2022 | 11.00.2100.60 | 11.0.3000.0 | 11.0.5058.0 | 11.0.6020.0 | 11.0.7001.0 | 11.0.7507.2 (Security for SP4 GDR) |
↓SQL Server 2008 R2 Version: 10.50 Mainstream support end: 8 July 2014 Extended support end: 9 July 2019 | 10.50.1600.1 | 10.50.2500 | 10.50.4000 | 10.50.6000 | 10.50.6560.0 (KB4057113) | |
↓SQL Server 2008 Version: 10.0 Mainstream support end: 8 July 2014 Extended support end: 9 July 2019 | 10.00.1600.22 | 10.00.2531 | 10.00.4000 | 10.00.5500 | 10.00.6000 | 10.00.6556.0 (KB4057114) |
↓SQL Server 2005 Version: 9.0 Mainstream support end: 12 April 2011 Extended support end: 12 April 2016 | 9.00.1399.06 | 9.00.2047 | 9.00.3042 | 9.00.4035 | 9.00.5000 | 9.00.5324 (MS12-070) |
↓SQL Server 2000 Version: 8.0 Mainstream support end: 8 April 2008 Extended support end: 9 April 2013 | 8.00.194 | 8.00.384 | 8.00.532 | 8.00.760 | 8.00.2039 | 8.00.2305 (MS12-060) |
↓SQL Server 7.0 Version: 7.0 Mainstream support end: 31 December 2005 Extended support end: 11 January 2011 | 7.0.623 | 7.0.699 | 7.0.842 | 7.00.961 | 7.00.1063 | 7.00.1152 (MS08-040) |
↓SQL Server 6.5 Version: 6.5 Mainstream support end: 30 June 1996 Extended support end: 1 January 2002 | 6.50.201 | See below | 6.50.416 (SP5a) | |||
↓SQL Server 6.0 Version: 6.0 Mainstream support end: 31 March 1999 | 6.00.121 | 6.00.124 | 6.00.139 | 6.00.151 | 6.00.151 (SP3) |
SQL Server 2019 build numbers
SQL Server | Analysis Services | Description | Release Date |
---|---|---|---|
15.0.4188.2 | 15.0.35.19 | CU14 for SQL Server 2019 (KB5007182) | 2021 November 22 |
15.0.4178.1 | 15.0.35.15 | CU13 for SQL Server 2019 (KB5005679) | 2021 October 5 |
15.0.4153.1 | 15.0.35.15 | CU12 for SQL Server 2019 (KB5004524) | 2021 August 4 |
15.0.4138.2 | 15.0.35.9 | CU11 for SQL Server 2019 (KB5003249) | 2021 June 10 |
15.0.4123.1 | 15.0.34.32 | CU10 for SQL Server 2019 (KB5001090) | 2021 April 6 |
15.0.4102.2 | 15.0.34.29 | CU9 for SQL Server 2019 (KB5000642) | 2021 February 11 |
15.0.4083.2 | Security update for SQL Server 2019 CU8 (KB4583459) | 2021 January 12 | |
15.0.4073.23 | 15.0.34.27 | CU8 for SQL Server 2019 (KB4577194) | 2020 October 1 |
15.0.4063.15 | 15.0.34.22 | CU7 (Removed) for SQL Server 2019 (KB4570012) | 2020 September 2 |
15.0.4053.23 | 15.0.34.21 | CU6 for SQL Server 2019 (KB4563110) | 2020 August 4 |
15.0.4043.16 | 15.0.34.19 | CU5 for SQL Server 2019 (KB4552255) | 2020 June 22 |
15.0.4033.1 | 15.0.34.14 | CU4 for SQL Server 2019 (KB4548597) | 2020 March 31 |
15.0.4023.6 | 15.0.34.9 | CU3 for SQL Server 2019 (KB4538853) | 2020 March 12 |
15.0.4013.40 | 15.0.34.1 | CU2 for SQL Server 2019 (KB4536075) HAS KNOWN ISSUE! | 2020 February 13 |
15.0.4003.23 | 15.0.32.52 | CU1 for SQL Server 2019 (KB4527376) | 2020 January 7 |
15.0.2080.9 | Security update for SQL Server 2019 GDR (KB4583458) | 2021 January 12 | |
15.0.2070.41 | 15.0.32.52 | Servicing Update (GDR1) for SQL Server 2019 RTM (KB4517790) | 2019 October 8 |
15.0.2000.5 | 15.0.32.50 | SQL Server 2019 RTM | 2019 November 4 |
15.0.1900.47 | Microsoft SQL Server 2019 Release Candidate Refresh for Big Data Clusters only (RC1.1) | 2019 August 29 | |
15.0.1900.25 | SQL Server 2019 RC1 (Release Candidate 1) | 2019 August 21 | |
15.0.1800.32 | SQL Server 2019 CTP 3.2 (Community Technology Preview 3.2) | 2019 July 24 | |
15.0.1700.37 | SQL Server 2019 CTP 3.1 (Community Technology Preview 3.1) | 2019 June 26 | |
15.0.1600.8 | SQL Server 2019 CTP 3.0 (Community Technology Preview 3.0) | 2019 May 22 | |
15.0.1500.28 | SQL Server 2019 CTP 2.5 (Community Technology Preview 2.5) | 2019 April 24 | |
15.0.1400.75 | SQL Server 2019 CTP 2.4 (Community Technology Preview 2.4) | 2019 March 26 | |
15.0.1300.359 | SQL Server 2019 CTP 2.3 (Community Technology Preview 2.3) | 2019 March 1 | |
15.0.1200.24 | SQL Server 2019 CTP 2.2 (Community Technology Preview 2.2) | 2018 December 11 | |
15.0.1100.94 | SQL Server 2019 CTP 2.1 (Community Technology Preview 2.1) | 2018 November 6 | |
15.0.1000.34 | SQL Server 2019 CTP 2.0 (Community Technology Preview 2.0) | 2018 September 24 |
SQL Server 2017 build numbers
SQL Server | Analysis Services | Description | Release Date |
---|---|---|---|
14.0.3421.10 | 14.0.249.83 | CU27 for Microsoft SQL Server 2017 (KB5006944) | 2021 October 27 |
14.0.3411.3 | 14.0.249.83 | CU26 for Microsoft SQL Server 2017 (KB5005226) | 2021 September 14 |
14.0.3401.7 | 14.0.249.75 | CU25 for Microsoft SQL Server 2017 (KB5003830) | 2021 July 12 |
14.0.3391.2 | 14.0.249.71 | CU24 for Microsoft SQL Server 2017 (KB5001228) | 2021 May 10 |
14.0.3381.3 | 14.0.249.70 | CU23 for Microsoft SQL Server 2017 (KB5000685) | 2021 February 24 |
14.0.3370.1 | Security updatefor Microsoft SQL Server 2017 CU22 (KB4583457) | 2021 January 12 | |
14.0.3356.20 | 14.0.249.54 | CU22 for Microsoft SQL Server 2017 (KB4577467) | 2020 September 10 |
14.0.3335.7 | 14.0.249.51 | CU21 for Microsoft SQL Server 2017 (KB4557397) | 2020 July 1 |
14.0.3294.2 | 14.0.249.36 | CU20 for Microsoft SQL Server 2017 (KB4541283) | 2020 April 7 |
14.0.3281.6 | 14.0.249.28 | CU19 for Microsoft SQL Server 2017 (KB4535007) | 2020 February 5 |
14.0.3257.3 | 14.0.249.21 | CU18 for Microsoft SQL Server 2017 (KB4527377) | 2019 December 9 |
14.0.3238.1 | 14.0.249.17 | CU17 for Microsoft SQL Server 2017 (KB4515579) | 2019 October 8 |
14.0.3223.3 | 14.0.249.14 | CU16 for Microsoft SQL Server 2017 (KB4508218) | 2019 August 1 |
14.0.3208.1 | On-demand hotfix update package for SQL Server 2017 CU15 (KB4510083) | 2019 July 10 | |
14.0.3192.2 | Security update for SQL Server 2017 CU15 GDR (KB4505225) | 2019 July 9 | |
14.0.3164.1 | On-demand hotfix update package for SQL Server 2017 CU15 (KB4506633) | 2019 June 20 | |
14.0.3162.1 | 14.0.249.3 | CU15 for Microsoft SQL Server 2017 (KB4498951) | 2019 May 24 |
14.0.3103.1 | 14.0.249.2 | Security update for SQL Server 2017 CU 14 GDR (KB4494352) | 2019 May 14 |
14.0.3076.1 | 14.0.245.1 | CU14 for Microsoft SQL Server 2017 (KB4484710) | 2019 March 25 |
14.0.3049.1 | FIX: On-demand hotfix update package for SQL Server 2017 CU13 (KB4483666) | 2019 January 8 | |
14.0.3048.4 | 14.0.239.1 | CU13 for Microsoft SQL Server 2017 (KB4466404) | 2018 December 18 |
14.0.3045.24 | 14.0.230.1 | CU12 for Microsoft SQL Server 2017 (KB4464082) | 2018 October 24 |
14.0.3038.14 | 14.0.228.1 | CU11 for Microsoft SQL Server 2017 (KB4462262) | 2018 September 21 |
14.0.3037.1 | 14.0.226.1 | CU10 for Microsoft SQL Server 2017 (KB4342123) | 2018 August 27 |
14.0.3035.2 | 14.0.223.1 | Security update for the remote code execution vulnerability in SQL Server 2017 (CU) (KB4293805) | 2018 August 14 |
14.0.3030.27 | 14.0.223.1 | CU9 for Microsoft SQL Server 2017 (KB4341265) | 2018 July 18 |
14.0.3029.16 | 14.0.223.1 | CU8 for Microsoft SQL Server 2017 (KB4338363) | 2018 June 21 |
14.0.3026.27 | 14.0.223.1 | CU7 for Microsoft SQL Server 2017 (KB4229789) | 2018 May 23 |
14.0.3025.34 | 14.0.204.1 | CU6 for Microsoft SQL Server 2017 (KB4101464) | 2018 April 17 |
14.0.3023.8 | 14.0.204.1 | CU5 for Microsoft SQL Server 2017 (KB4092643) | 2018 March 20 |
14.0.3022.28 | 14.0.204.1 | CU4 for Microsoft SQL Server 2017 (KB4056498) | 2018 February 20 |
14.0.3015.40 | 14.0.202.1 | CU3 for Microsoft SQL Server 2017 (KB4052987) Security Update for SQL Server 2017 CU3 RTM (KB4058562) | 2018 January 3 |
14.0.3008.27 | 14.0.1.440 | CU2 for Microsoft SQL Server 2017 (KB4052574) | 2017 November 28 |
14.0.3006.16 | 14.0.1.439 | CU1 for Microsoft SQL Server 2017 (KB4038634) | 2017 October 24 |
14.0.2037.2 | Security update for SQL Server 2017 GDR (KB4583456) | 2021 January 12 | |
14.0.2027.2 | Security update for SQL Server 2017 GDR (KB4505224) | 2019 July 9 | |
14.0.2014.14 | 14.0.6.443 | Security update for SQL Server 2017 GDR (KB4494351) | 2019 May 14 |
14.0.2002.14 | 14.0.3.441 | Security update for the remote code execution vulnerability in SQL Server 2017 (GDR) (KB4293803) | 2018 August 14 |
14.0.2000.63 | 14.0.3.441 | Security Update for SQL Server 2017 GDR (KB4057122) | 2018 January 3 |
14.0.1000.169 | 14.0.1.439 | SQL Server 2017 (vNext) RTM | 2017 October 2 |
14.0.900.75 | SQL Server 2017 (vNext) RC2 (Release Candidate 2) | 2017 August 2 | |
14.0.800.90 | SQL Server 2017 (vNext) RC1 (Release Candidate 1) | 2017 July 17 | |
14.0.600.250 | SQL Server 2017 (vNext) CTP 2.1 (Community Technology Preview 2.1) | 2017 May 17 | |
14.0.500.272 | SQL Server 2017 (vNext) CTP 2.0 (Community Technology Preview 2.0) | 2017 April 19 | |
14.0.405.198 | SQL Server vNext CTP 1.4 (Community Technology Preview 1.4) | 2017 March 18 | |
14.0.304.138 | SQL Server vNext CTP 1.3 (Community Technology Preview 1.3) | 2017 February 17 | |
14.0.200.24 | SQL Server vNext CTP 1.2 (Community Technology Preview 1.2) | 2017 January 20 | |
14.0.100.187 | SQL Server vNext CTP 1.1 (Community Technology Preview 1.1) | 2016 December 16 | |
14.0.1.246 | SQL Server vNext CTP 1 (Community Technology Preview 1) | 2016 November 16 |
SQL Server 2016 build numbers
SQL Server 2014 build numbers
SQL Server 2012 build numbers
SQL Server 2008 R2 build numbers
SQL Server 2008 build numbers
SQL Server 2005 build numbers
SQL Server 2000 build numbers
Build | Description | Release Date |
---|---|---|
8.00.2305 | MS12-060: Security update for SQL Server 2000 Service Pack 4 QFE (KB983811) | 2012 August 14 |
8.00.2039 | SQL Server 2000 Service Pack 4 | 2005 May 6 |
8.00.760 | SQL Server 2000 Service Pack 3/3a | 2003 May 19 |
8.00.532 | SQL Server 2000 Service Pack 2 | 2001 November 30 |
8.00.384 | SQL Server 2000 Service Pack 1 | 2001 June 12 |
8.00.194 | SQL Server 2000 RTM | 2000 November |
SQL Server 7.0 build numbers
Build | Description | Release Date |
---|---|---|
7.00.1063 | SQL Server 7.0 Service Pack 4 | 2002 April 26 |
7.00.961 | SQL Server 7.0 Service Pack 3 | 2000 December 15 |
7.00.842 | SQL Server 7.0 Service Pack 2 | 2000 March 20 |
7.00.699 | SQL Server 7.0 Service Pack 1 | 1999 July 1 |
7.00.623 | SQL Server 7.0 RTM | 1998 November 27 |
SQL Server 6.5 build numbers
Build | Description | Release Date |
---|---|---|
6.50.416 | SQL Server 6.5 Service Pack 5a | 1998 December 24 |
6.50.415 | SQL Server 6.5 Service Pack 5 | |
6.50.281 | SQL Server 6.5 Service Pack 4 | |
6.50.258 | SQL Server 6.5 Service Pack 3a | |
6.50.252 | SQL Server 6.5 Service Pack 3 | |
6.50.240 | SQL Server 6.5 Service Pack 2 | |
6.50.213 | SQL Server 6.5 Service Pack 1 | |
6.50.201 | SQL Server 6.5 RTM | 1996 June 30 |
SQL Server 6.0 build numbers
Build | Description | Release Date |
---|---|---|
6.00.151 | SQL Server 6.0 Service Pack 3 | |
6.00.139 | SQL Server 6.0 Service Pack 2 | |
6.00.124 | SQL Server 6.0 Service Pack 1 | |
6.00.121 | SQL Server 6.0 RTM |
More details you can find at sqlserverbuilds.blogspot.com
Thanks for compiling this info. I spotted an incorrect date under SQL 2012 for 11.0.5644.2 – I believe it should be Jan 2016 rather than 2015. The same issue may also be true for 11.0.6518, but this was not as clear given the mix of dates for fixed package file info.
Fixed. Thank you.
Looks like 12.0.4213.0 is missing (KB3070446)
Fixed. Thank you.
SSMS 2016 (SQL Server Management Studio) build numbers appear to be relevant now, since they are no longer tied to the SQL Server. Could SSMS be included on the page?
SSMS July 2016 13.0.115500.91
SSMS June/GA release June 2016 13.0.15000.23
SSMS April 2016 Preview (13.0.14000.36)
SSMS March 2016 Preview Refresh (13.0.13000.55)
SSMS March 2016 Preview (13.0.12500.29)
SSMS February 2016 Preview (13.0.12000.65)
SSMS January 2016 Preview (13.0.11000.78)
— no longer in-sync with SQL Server build numbers
SSMS December 2015 Preview (13.0.900.73)
SSMS November 2015 Preview (13.0.800.111)
SSMS October 2015 Preview (13.0.700.242)
SSMS September 2015 Preview (13.0.600.65)
SSMS August 2015 Preview (13.0.500.53)
SSMS July 2015 Preview (13.0.400.91)
SSMS June 2015 Preview (13.0.300.44)
Done
Hi there Andrey,
I just saw that the link for MS-SQL 2012 update on Sept 20 2016 for 11.0.6544.0 from KB3180915 appears incorrect. I did find the download page for that KB, but it seems to be a Spanish language page at https://www.microsoft.com/es-es/download/details.aspx?id=50733, and the link on that page under ‘Details’ has the same problem as the link you published.
Andy
Hi Andy. The link is ok now. This happens from time to time with KB articles for just released updates.
Latest SSMS has yet to appear on the list: “SSMS 16.4.1 (September 2016) release” Generally available Build number: 13.0.15900.1
Thanks
Thanks
There is a new silent release to fix some pain in the arse bugs in SQL 2016 CU2 SSAS…
https://support.microsoft.com/en-us/kb/3199171
Thank you!
There are two build number typos (12.x…) in the SQL Server 2012 section.,,
Corrected. Thank you.
My SQL Server 2014 with SP2 CU3 shows build number 12.0.5538
Yes. Seems like initially it was wrong number in the KB. Thank you.
14.0.200.24 SQL Server vNext CTP1.2 (Community Technology Preview 1.2) 2016 Janury 20 typo error : 20 jan 2017
Great resource, by the way…
12.0.5388.0 MS16-136: Security Update for SQL Server 2012 Service Pack 3 GD2 (KB3194719) 2016 November 8 – shouldn’t it be 11.0.5388.0?
Opps, typo. Thank you!
also, should this be ‘Service pack 2’? not SP3.
Hi,
You appear to be missing CU8 for SQL Server 2012 SP3(KB4013104) Build Number: 11.0.6594.0
Thanks for maintaining this list. I use it to update my DB that monitors my estate and reports back updates required 😀
Thanks! I’m glad that the list is helpful 🙂
Thank you for this list. This had version numbers that the Microsoft documentation didn’t have.
Appreciate it.
Newest SSMS version: 17.1 is build 14.0.17119.0
Thanks.
2016 CU5 (build number: 13.0.4451.0) is now available from:
https://support.microsoft.com/en-us/help/4040714/cumulative-update-5-for-sql-server-2016-sp1
Thanks!
Hello there, just letting you know that your link for SQL 2012 SP4 is for Russian language rather than (your usual) English. Try link https://support.microsoft.com/en-us/help/4018073/sql-server-2012-service-pack-4-release-information instead
Nice catch. Thank you
Thank you, man! Very good job!
This is a great resource and actually it is always on top of my Google search result when I try to find SQL Server build numbers. However, could I propose that you change “SQL Server vNext build numbers” to “SQL Server 2017 build numbers”? SQL Server 2017 was officially released on Oct 2017, so it is not vNext (i.e. it is already named)
Done 🙂
Please add: SSMS 17.4 released on Dec 7, 2017. Thx !
Done. Thank you.
Thanks Andrey. One thing I need to mention is that you have lots of typos for a specific month, i.e January Your typo is Janury (missing letter ‘a’). Why do I notice this? 🙂 because I am building my sql server version inventory table based on this website.
Ouch.. fixed everything I found. Thanks!
Thanks !
Just FYI, Andrey, I wrote a tip based on your info at this website page. Thanks for your efforts!
https://www.mssqltips.com/sqlservertip/5282/creating-a-sql-server-build-and-patch-release-table/
Cool!
Thanks for providing this list. Just saw a typo:
January 6 update for SQL 2008 R2 is build 10.50.6560.0 not 10.50.6556.0
Thanks!
https://support.microsoft.com/ta-in/help/4091266/on-demand-hotfix-update-package-for-sql-server-2012-sp4 was recently released, SQL 2012 hotfix, Build 11.0.7469.6 listed on the page.
Added, thank you.
Hi Andrey,
I would like to use your page as a reference to a PowerShell checking script I have written. I have referenced your site in the script. Are you OK for me to do this?
I am happy to provide you the script if you would like?
Thanks!
Hi Sean,
I’m absolutely OK with it 🙂
Hi, SSMS 17.7 has been released.
https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017
Added, thank you
Hi,
Alot of the SQL Server 2008 R2 servers return a 4th segment in their Build Numbers. Is it possible to reflect this on the tables?
I currently Skim the site for the patches in order to match against what my servers report against what the latest is to identify the patching requirements however 2008 R2 is not matching up because of these 4th segments.
Thanks
SQL 2017 RTM CU7 has been released, KB 4229789
https://www.microsoft.com/en-us/download/details.aspx?id=56128
13.0.4502.0 CU8 for Microsoft SQL Server 2016 SP1 (KB4100997) 2018 May 29
The Hyperlink text should read “CU9” 🙂
Fixed. Thanks 🙂