Latest Builds of SQL Server 2016


Service Pack 2 Branch

Service Pack 2 was released on April 9th, 2018, with a build number of 13.0.5026.0, with 75 fixes and enhancements published in KB #4052908 Also included (but not documented explicitly in the SP2 KB) are all fixes included in every SP1 Cumulative Update to this point, including everything in SP1 Cumulative Update #8

Since then, cumulative updates have been published. You can always download the latest CU for the SP2 branch here.

Builds
Label Build # Release Date Build Date Fixes (Public)
Cumulative Update #6 13.0.5292.0 2019-03-19 2019-03-12 29 (24)
Cumulative Update #5 13.0.5264.1 2019-01-23 2019-01-11 52 (43)
On-Demand Hotfix for SP2 CU #4
KB #4482972
13.0.5237.0 2018-12-20 2018-12-03 3 (3)
Cumulative Update #4 13.0.5233.0 2018-11-13 2018-11-03 42 (36)
Cumulative Update #3 13.0.5216.0 2018-09-20 2018-09-14 41 (27)
DO NOT USE - see the warning in KB #4458871.
CVE-2018-8273 (CU)
KB #4458621
(Download)
13.0.5201.2 2018-08-20 2018-08-18 1
The original release for the SP2 CU security fix (below) had some undocumented trace flags enabled, and so the patch was pulled and re-released (see this post and this post).
CVE-2018-8273
KB #4293807
Pulled
13.0.5161.0 2018-08-14 2018-07-18 1
Cumulative Update #2 13.0.5153.0 2018-07-16 2018-06-29 29 (21)
Cumulative Update #1 13.0.5149.0 2018-06-27 2018-06-23 45 (28)
SP2 GDR builds below – for non-CU path (don't do this)
CVE-2018-8273 (GDR)
KB #4293802
(Download)
13.0.5081.1 2018-08-22 2018-08-18 1
Service Pack 2 13.0.5026.0 2018-04-09 2018-03-19

75 (75)

Download Service Pack 2 here, and the latest build of SQL Server 2016 Express is now available here.  Keep in mind, though, that you can apply the service pack to an existing version of SQL Server Express (RTM or SP1).

Service Pack 1 Branch

Service Pack 1 was released on November 16th, 2016, with a build number of 13.0.4001.0, and 33 total fixes and enhancements publicized in KB #3182545

The Big News
A few questions

The following questions have come up since SP1 was released:

      • Does it include the MSVCRT fix from post-RTM? Yes. If you apply SP1 after installation or using slipstream, you do not have to apply the MSVCRT update separately.
      • Does it include MS16-136? Yes. The security bulletin from earlier this month is in SP1, even if the bulletin and the SP1 article don't say so explicitly.
      • Does it include everything in RTM Cumulative Update #3? Yes.
A few words of warning

A couple of observations you'll want to keep in mind:

      • SP1 produces a new ShowPlan schema, so trying to open plans by double-clicking an XML column in a grid result might lead to an XML document as opposed to a graphical plan. To work around this, you can install the SSMS 17.0 RC1 and either (a) use the RC for your cache-diving or (b) copy the ShowPlanXML.XSD from the 17.0 installation path into the 16.x path. These paths are typically going to be:
        New (17.0)
        %Program Files%\Microsoft SQL Server\140\Tools\Binn\schemas\sqlserver\2004\07\showplan\
        Old (16.x)
        %Program Files%\Microsoft SQL Server\130\Tools\Binn\schemas\sqlserver\2004\07\showplan\
      • In their blog post, Microsoft recommends planning for a reboot after the SP1 installation (this likely depends on which features and components you have installed).

Finally, you can always download the latest Cumulative Update for SP1 from the Download Center. If you want older updates, check the Microsoft Update Catalog.

Builds

Label Build # Release Date Build Date Fixes (Public)
Cumulative Update #14 13.0.4560.0 2019-03-19 2019-03-12 7 (7)
Cumulative Update #13 13.0.4550.1 2019-01-23 2019-01-11 12 (9)
Cumulative Update #12 13.0.4541.0 2018-11-13 2018-10-27 21 (16)
Cumulative Update #11 13.0.4528.0 2018-09-17 2018-08-31 14 (8)
CVE-2018-8273 (CU)
KB #4293808
(Download)
13.0.4522.0 2018-08-14 2018-07-18 1
Cumulative Update #10 13.0.4514.0 2018-07-16 2018-06-23 26 (21)
Cumulative Update #9 13.0.4502.0 2018-05-30 2018-05-15 39 (25)
Cumulative Update #8 13.0.4474.0 2018-03-19 2018-02-24 57 (37)
Cumulative Update #7 13.0.4466.4 2018-01-03 2017-12-22 29 (22)
Cumulative Update #6 13.0.4457.0 2017-11-21 2017-11-09 55 (41)
Cumulative Update #5 13.0.4451.0 2017-09-18 2017-09-06 49 (44)
Cumulative Update #4    13.0.4446.0    2017-08-08 2017-07-16 63 (49)
Cumulative Update #3    13.0.4435.0    2017-05-15 2017-04-27 70 (57)
Cumulative Update #2    13.0.4422.0    2017-03-20 2017-03-06 117 (100)
Cumulative Update #1    13.0.4411.0    2017-01-18 2017-01-06 63 (55)
SP1 GDR builds below - for non-CU path
CVE-2018-8273 (GDR)
KB #4458842
(Download)
13.0.4224.16 2018-08-22 2018-08-18 1
The original release for the SP1 GDR security fix (below) caused an issue with CEIP, and so the patch was pulled and re-released (see this post).
CVE-2018-8273 (GDR)
KB #4293801
Pulled
13.0.4223.10 2018-08-14 2018-07-18 1
Security Advisory ADV180002
KB #4057118 (GDR)
   13.0.4210.6    2018-01-03 2017-12-23 1 (1)
Security Bulletin CVE-2017-8516
KB #4019089 (GDR)
   13.0.4206.0    2017-07-16 2017-07-07 1 (1)
COD Hotfix 3210089
(GDR - MDS Update)
   13.0.4202    2016-12-16 2016-12-13 3 (3)
COD Hotfix 3207512
(GDR - SSRS Update)
   13.0.4199    2016-11-23 2016-11-18 2 (2)
Service Pack 1    13.0.4001    2016-11-16 2016-10-28 33 (33)
Other articles

Other articles about this exciting release:

 

RTM Branch

SQL Server 2016 RTM was released on June 1st, 2016, with a build number of 13.0.1601.5.

See the announcement posts here and here, a 10-minute Channel 9 video here, and the updated edition feature comparison here.

The latest RTM Cumulative Update can always be obtained from the Download Center (older builds can be obtained from the Microsoft Update Catalog).

 

Label Build # Release Date Build Date Fixes (Public)
Security Advisory ADV180002
KB #4058559 (CU)
   13.0.2218.0    2018-01-06 2017-12-28 1 (1)
Cumulative Update #9    13.0.2216.0    2017-11-21 2017-11-09 26 (21)
Cumulative Update #8    13.0.2213.0    2017-09-18 2017-09-06 19 (17)
Cumulative Update #7    13.0.2210.0    2017-08-08 2017-07-16 33 (30)
Cumulative Update #6    13.0.2204.0    2017-05-15 2017-04-20 28 (22)
Cumulative Update #5    13.0.2197.0    2017-03-20 2017-02-25 56 (47)
Cumulative Update #4    13.0.2193.0    2017-01-18 2017-01-06 65 (57)
COD Hotfix for CU3 (MDS)    13.0.2190.2    2016-12-16 2016-12-13 3 (3)
Cumulative Update #3
Security Bulletin MS16-136
KB #3194717
   13.0.2186.6    2016-11-08 2016-10-31 31 (31)
To try to explain here, CU3 was officially released on November 16th, but the security update that was released on November 8th actually already included all of the fixes in the CU. So it doesn't really matter where you get this build, it will update you to the latest. Trying to install CU3 over MS16-136 won't work.
COD Hotfix 3199171    13.0.2170.0    2016-11-01 2016-10-11 4 (4)
COD Hotfix 3195813    13.0.2169.0    2016-10-26 2016-10-05 4 (4)
Cumulative Update #2    13.0.2164.0    2016-09-22 2016-09-09 68 (64)
Cumulative Update #1    13.0.2149.0    2016-07-25 2016-07-11 192 (146)

Three big questions come from this CU release.

  1. Does it include the MSVCRT GDR fix?
    Yes, I have confirmation from the SQL Server team that the GDR fix from KB #3164398 is included, even though it is not currently listed in the KB article.
  2. Why are there fixes that seem to apply to SSMS?
    Right, SSMS is separate, so updates to it shouldn't be included in an engine CU. However, keep in mind that the CU applies to other parts of the system besides the engine, like shared components. Some fixes, for example, apply to underlying SSIS components and other binaries used by things like maintenance plans, and may need to be maintained independent of a local copy of SSMS (if one even exists).
  3. Why are there both x64 and x86 packages?
    As above, while there is no x86 engine, fixes can apply to a variety of shared components on the machine (including from the feature pack), and I suppose it's possible that those could be installed in isolation on an x86 machine. It is almost certainly the case that if you have installed SQL Server 2016, you should be applying the x64 CU, and only the x64 CU. I will update this space if I get further clarification about this.

Also, some people seem to have an issue getting their browser to properly display the download overlay, where they can choose the x64 and/or the x86 file; instead they get redirected to the confirmation page with no prompt to download. I suggest either using a different browser or a direct link: x64 | x86

RTM & GDR builds below - for non-CU path
Security Advisory ADV180002
KB #4058560 (GDR)
   13.0.1745.2    2018-01-06 2017-12-30 1 (1)
Security Bulletin CVE-2017-8516
KB #4019088 (GDR)
   13.0.1742.0    2017-07-16 2017-07-07 1 (1)
GDR Update (MDS)    13.0.1728.2    2016-12-16 2016-12-13 3 (3)
Security Bulletin MS16-136
KB #3194716
   13.0.1722.0    2016-11-08 2016-10-31 1 (1)
MSVCRT GDR
(KB #3164398)
   13.0.1708.0    2016-06-04 2016-06-02  
RTM    13.0.1601.5    2016-06-01 2016-04-29 N/A

Where to Download

You can download SQL Server 2016 from TechNet Evaluation Center, MSDN Subscriber Downloads, Visual Studio Dev Essentials, or your own Volume License server(s). If you are looking for the now free Developer Edition specifically, see this recent post, "Where do I get Developer Edition?"

SQL Server Management Studio

In the spirit of the separate release of Management Studio, we've moved information about new builds (along with SSDT) to a separate page.

Pre-Release Builds

Looking for information about the betas (CTPs and RCs)? We've moved that information, too.

These posts are provided by the collective SentryOne team!


Comments