SentryOne Team Blog (

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.

    Label Build # Release Date Build Date Fixes (Public)
    Cumulative Update #7 13.0.5337.0 2019-05-22 2019-05-16 28 (27)
    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
    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).
    KB #4293807
    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
    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
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)
    Please see the Spectre/Meltdown blurb above for more details.
    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)
    Please see the Spectre/Meltdown blurb above for more details.
    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)
    (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.

New call-to-action

Join the Conversation

  1. According to you chart there are a lot of unpublished KB's for SP1 CU8. I've heard the arguments but it still makes you wonder.

  2. I just performance tested CU7 on SQL 2016 SP1 and found a 28% decrease in the application's ability to support multiple users and a 50% increase in average response times. The metric SQLServer:Wait Statistics(Average wait time (ms))\Non-Page latch waits increased 10-fold

  3. Where can I find information on the 13.1.x.x builds? (i.e. 13.1.4001.0)
    How do they differ from the 13.0.x.x versions?

    1. Where are you seeing 13.1.x.x? Probably by looking at file properties. There is no difference, it's just that certain file versioning uses a different build hierarchy. Stick to the results of SELECT @@VERSION; or SELECT SERVERPROPERTY('ProductVersion');.

  4. Probably a mix of all of that !! :)
    But only one thing is important at the end of the story: a lot of improvements with this release !! :)

    1. I guess you missed the Connect() keynote,, all the new features they added, and the change they made to how SKUs work for many programmability features?

      You're right, typically, Service Packs come out roughly a year after initial release, give or take. You could speculate a number of reasons behind this fast-tracked release.

      • They wanted to announce this SKU change and the new features along with other exciting announcements, like the first public CTP of v.Next, to get maximum eyeballs during Connect().
      • They got sick of people complaining for a year after previous releases that service pack 1 isn't out yet.
      • They wanted to eliminate the argument people make that they won't upgrade to a new release until SP1 is out (a lame argument in general, IMHO).
      • Standard Edition sales may be slumping – why not do something dramatic that will punch it in the gut this year instead of waiting until next June?
  5. No Aaron, i read it on Microsoft's KB pages like you, i didn't download it. The only one i had personally downloaded (via microsoft email) is KB3195813 (13.0.2169).

    Actually, as far as i understand, the situation is:

    KB3195813: Only one effectively downlodable, contains 4 fix (KB3195901, KB3189855, KB3195825, KB3197952) and raise version to 13.0.2169

    KB3195901 / KB3189855: Microsoft says that "After you apply this hotfix, the SQL Server version is 13.0.2170.0" but there is no download button, only a link to KB3195813

    KB3195825: Microsoft don't say anything about version level, and provide only a link to KB3195813

    KB3197952: Microsoft says that "After you apply this hotfix, the SQL Server version is 13.0.2170.0", provide a non-working download button AND a link to KB3195813

    Weird and ugly!!

    Anyway, at the end of the story, i think that the right (and actually only) choice is to install KB3195813 (13.0.2169) and ignore anything else, or even better wait for CU3.

    If you can get some clarification from MS please share with us, i'm curious! :)
    Thank you, also for this useful blog!! :)

  6. Hi.. someone knows why hotfix 3195813 elevate version level at 13.0.2169, but three of four fix included (3195901, 3189855 and the only one listed above 3197952) elevate version level at 13.0.2170 ?

    Is not a little bit confusing ?

    (for example if i install only one of these fix i see an higher version -13.0.2170- , but i have online only one of these 3-4 fix)

    1. I've actually already got in a request about this and hope to provide an update soon.

      But, which hotfix were you able to download to get you to 2170? This one *says* there is a download available, but if you click through, you can't get to it. The other three fixes didn't even have a download button when I checked.

  7. We use Event Notifications to collect DDL events in a centralized server using the service broker on the audited servers. It all exploded as soon as I installed CU2.

    The error message that is thrown to the incoming connection is:
    "An error occurred while receiving data: '24(The program issued a command but the command length is incorrect.)'."

    The remote server generates a logs entry with:
    "An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Initiator, far endpoint address: '')" (IP address changed).

    I went ahead and uninstalled the CU and it all went back to normal right away.

  8. I know Datazen is been implemented in 2016 Reporting services. One of challenge in Datazen, it doesnt give a feature to download KPI in Excel or PDF. Can you please confirm 2016 has this feature to download KPI dashboard in excel or PDF. One of the Microsoft resource mentioned that it will be getting added in a post-RTM release of the product. But, still now this feature is not available.

    1. Sorry Selvaraju, I don't know anything about Datazen, and wouldn't know who to ask. I didn't see anything about it explicitly in either of these Cumulative Updates, but I wasn't watching for it, either…

  9. SSMS restore database task doesn't work. Moving a .bak file to different locations generates different errors : ranging from permission denied exceptions to 'cannot find Table 0' to simply not appearing in the GUI selector for the file.

    The SSMS version is the latest July 2016 Hotfix.

    SSMS is run as Administrator on both a Win Server 2012 R2 and Win 8.1. Owner of the .bak files is Adminstrator with Full Control.

    Please advise.


  10. A small bug that I raised connect incident 2979531 on. If you install R services it creates number of local Windows accounts. If you uninstall R services and try and re-install it will complain over the fact the account already exist. In my case I was taking a server from RC2, I uninstalled SQL2016, to RTM to CU1. I had to remove in my case the 20 local accounts created before I could install R services.

  11. Did Intellisence get fixed in SSMS 2016?

    What bugs me most day-to-day in 2012/2014 is how messed up Intellisense got. It stopped working across VPN's and no longer showed field lengths/properties with the Data Types (for example in 2012/2014 it will say "NVARCHAR" but not "NVARCHAR(70)") I hope 2016 has brought back Intellisense Sanity.

    1. Hi Jonathan, if you have a slow VPN then, yeah, as IntelliSense tries to pull more data, I would expect it to behave erratically (perhaps more data for internal reasons, perhaps more data because your metadata got larger, perhaps because they tightened up the timeouts, perhaps a combination).

      I'm not sure I understand your second comment. Could you show an example of this nvarchar vs. nvarchar(50)? Where exactly are you seeing this difference? Some of that may not be IntelliSense's fault directly – much of the information is derived from elsewhere, e.g. how it describes/defines a function. SERVERPROPERTY, for example, says property_name is varchar(1), but we all know that's incorrect.

      1. Update Rollup 4 for System Center 2012 R2 Data Protection Manager came with suport for SQL Server 2014 but I can't find any new on the status for DPM support for SQL Server 2016. Is there support for it?

  12. Hello, I know this question might be a little uncertain but I you were to gamble when in the future do you think would be the RTM release date. How much time longer would be good to wait. The reason for this question is that I am about to migrate around 70 production SQL databases to new servers and since is needed to make a downtime. I was thinking it would be a good idea to install and migrate everything to SQL Server 2016 RTM at once instead of using SQL Server 2014 SP1 and upgrading later sometime in the future, that's only if the release date is no longer than three weeks from now.

  13. Have you gotten any feedback from them when we might expect the Power BI on-premise integrations with SSRS to be released? Whether that is something on the roadmap for a future SP or whatever the case may be?

  14. I'm having a bit of an issue trying to upgrade CTP 3.2 to CTP 3.3. I open the setup program, go to Installation, select "Upgrade from a previous version…" and run through the rules, selecting the default instance. All of the features get auto checked, which his good…but when I click next and it goes to the Instance Configuration page, it greys out the top options and automatically puts in a new Instance ID of MSSQLSERVER1000 and puts that into a new C:\ path instead of using the currently installed path. So even doing the upgrade, it seems to want to install a side by side version instead of doing an in-place upgrade. Did I miss any documentation saying that you can't do in-place upgrades on the CTP versions or is there something I need to do to make this work?

    1. Jacob, sorry, I haven't come across that issue, my upgrades have been smooth. However, in almost every case, I have performed a side-by-side install. I just find that it's easier and cleaner to do it that way; I don't really gain anything by upgrading a test evaluation instance.

  15. Regarding AT TIME ZONE and your notes "… So, it is still an incomplete solution, because you need to know whether to declare the destination time zone as standard or daylight… "

    That is incorrect. The time zone string specified such as "Pacific Standard Time" is the ID for the time zone. It applies to the entire Pacific time zone, including PST and PDT. In other words, you do not need to pre-determine if DST is in effect and pass "Pacific Daylight Time". That actually wouldn't work, since "Pacific Daylight Time" is not a Windows time zone ID.

    Basically, these are the same IDs used by .NET's TimeZoneInfo object, and can also be found in the registry or via tzutil.exe.

    Windows time zone names are a common source of confusion. Read the section titled "The Microsoft Time Zone Database" in this article:

    1. Thanks Matt, I stand corrected. I knew that the daylight variations were not Windows time zones, but I didn't test the output for both a date in DST and a date outside of it. I only played with it for a few minutes before posting, it just seemed from the DMV that is_currently_dst would somehow be used to determine whether to apply a DST shift. I'm quite happy to learn it's more intelligent than that.

    1. I think you may be over-reacting about one isolated case, two months ago, where a user somehow managed to install CTP 2.1 on an operating system that SQL Server 2016 does not officially support, and should have installed on a VM or test machine rather than his primary workstation (which is what most people do with betas anyway). If you contrast all of those facts with the number of people who can't uninstall official Evaluation Edition releases (see the comments on this post), I don't think there is any need for widespread panic about a beta.

      1. Well, it's a beta. If you install ANY beta software on a server that matters, more the fool you. You can't blame Microsoft or any other company for a product that is clearly labelled as such. So panic away, but don't tell anyone what a dimwit you are :)

  16. There is a problem in SQL Server 2016 CTP 2.2 with Master Data Services. Explorer is deactivated. You can create a model and entity but you can't explore data. Also in home page I am able to select the model but not the Version as it is always appears to be empty. The strange thing is that I am able to select the Versions through Version Management as well as from Integration Management.

  17. The 2.2 problem appears to be fixed.

    UPDATE: The issue with the initial release SQL Server 2016 CTP 2.2 that caused downtime during rolling upgrades across an AlwaysOn Availability Group has been corrected, and the download replaced. The download link now points to an updated build of 13.0.407.1 or higher. An upgrade to this build is recommended for all users of SQL Server 2016, including AlwaysOn users. For more information, visit the CTP 2.2 Release Note.

  18. From the SQL Server Blog

    UPDATE: There is an issue with the SQL Server 2016 CTP 2.2 release that causes downtime during rolling upgrades across an AlwaysOn Availability Group. If you are not using AlwaysOn, you will not experience the issue. We recommend that AlwaysOn users not upgrade to CTP 2.2 at this time. A replacement build of SQL Server 2016 CTP 2.2 is in process and will be available soon. For more information, visit the CTP 2.2 Release Note.