SentryOne Team Blog (

Latest Builds of SQL Server 2014

Service Pack 3 Branch

On October 30th, 2018, Microsoft released SQL Server 2014 Service Pack 3. This will almost certainly be the final service pack for SQL Server 2014; you should start thinking about your upgrade strategy now, because history tells us the older SP branches will quickly slip out of maintenance mode.

The build number for SP3 is 12.0.6024.0 and there are 31 fixes documented in KB #4022619. Many of these improvements are updates that have been back-ported after being implemented in SQL Server 2016, 2017, and 2019. The service pack includes fixes from the SP2 branch up to and including Cumulative Update #13 (the fixes from CU #14 will follow).

Build Name Build # KB Article Date New fixes (public)
SP3 Cumulative Update #2    12.0.6214.1    KB #4482960 2019-02-19 5 (5)
SP3 Cumulative Update #1    12.0.6205.1    KB #4470220 2018-12-12 16 (13)
Service Pack 3    12.0.6024.0    KB #4022619 2018-10-30 31 (31)

You can download the full edition here and the new Express Edition is available here. The updated feature pack should be available sometime in November.


Microsoft has changed their servicing model slightly, in that for any particular branch, the CU download page only offers the most recent Cumulative Update. This is true no matter which KB article you came from. However, if you are looking for a specific Cumulative Update that doesn't happen to be the most recent one, you can download it from the Microsoft Update Catalog – just don't expect that to always have the latest.

Regardless of your branch or patch level, be sure to check out this CSS blog post and KB #2964518 : Recommended updates and configuration options for SQL Server 2012 / 2014, which is full of useful advice.

For help with acronyms used here or in the resources referenced, see Definitions of SQL Server release acronyms.

And of course, please always perform full regression testing before installing any SQL Server update in production. Kendra Little has a nice post about this.

Service Pack 2 Branch

Service Pack 2 (12.0.5000) was released on July 11, 2016, and includes 133 fixes and enhancements – including all of the fixes up to and including SP1 CU7. Those from SP1 CU8 should all be found in SP2 CU1, released August 25th. The official Knowledge Base article for SP2 is KB #3171021, and you can download the service pack here and the updated feature pack here. The latest CU for SQL Server 2014 Service Pack 2 is always available here, except in the case of certain out-of-band security updates, like Spectre/Meltdown (more info below).

Build Name Build # KB Article Date New fixes (public)
SP2 Cumulative Update #16    12.0.5626.1    KB #4482967 2019-02-19 3 (3)
SP2 Cumulative Update #15    12.0.5605.1    KB #4469137 2018-12-12 8 (7)
SP2 Cumulative Update #14    12.0.5600.1    KB #4459860 2018-10-15 8 (6)
SP2 Cumulative Update #13    12.0.5590.1    KB #4456287 2018-08-28 4 (4)
SP2 Cumulative Update #12    12.0.5589.7    KB #4130489 2018-06-18 27 (16)
SP2 Cumulative Update #11    12.0.5579.0    KB #4077063 2018-03-19 12 (10)
SP2 Cumulative Update #10
Security Advisory
ADV180002 (CU10)
   12.0.5571.0    KB #4057117
KB #4052725
2018-01-16 5 (4)
SP2 Cumulative Update #9 12.0.5563 KB #4055557 2017-12-18 8 (7)
SP2 Cumulative Update #8 12.0.5557 KB #4037356 2017-10-17 15 (8)
SP2 Cumulative Update #7 12.0.5556 KB #4032541 2017-08-28 15 (8)
SP2 Cumulative Update #6 12.0.5553 KB #4019094 2017-08-08 29 (29)
SP2 Cumulative Update #5 12.0.5546 KB #4013098 2017-04-17 24 (21)
SP2 Cumulative Update #4 12.0.5540 KB #4010394 2017-02-21 30 (27)
SP2 Cumulative Update #3 12.0.5538 KB #3204388 2016-12-28 44 (39)
Security Bulletin
MS16-136 (CU)
12.0.5532 KB #3194718 2016-11-08 1 (1)
SP2 Cumulative Update #2 12.0.5522 KB #3188778 2016-10-18 18 (18)
SP2 Cumulative Update #1 12.0.5511 KB #3178925 2016-08-24 45 (36)
SP2 GDR builds below – for non-CU path
Security Advisory
ADV180002 (GDR)
   12.0.5214    KB #4057120    2018-01-16    1 (1)
Security Bulletin
CVE-2017-8516 (GDR)
12.0.5207 KB #4019093 2017-08-08 1 (1)
Security Bulletin
MS16-136 (GDR)
12.0.5203 KB #3194714 2016-11-08 1 (1)
Service Pack 2 12.0.5000 KB #3171021 2016-07-11 133 (53)

Some very interesting improvements in Service Pack 2, many of which were already included in SQL Server 2016. There were others, so this list should not be considered exhaustive, just OUR TOP 20:

Service Pack 1 Branch (Retired)

Service Pack 2 has been released, and it really should be where your efforts are going, if it is possible (yes, I know some people have to stay on older service packs for a variety of reasons).

RTM Branch (Retired)

If you're on RTM still (< 12.0.4000), there is an important security GDR/QFE that has been released through Security Bulletin MS15-058 and KB #3065718. This issue does not affect Service Pack 1. (And you should start planning to move to the SP2 branch now anyway.)

New call-to-action

54 replies on “Latest Builds of SQL Server 2014”

54 Comments (Comments are now closed.)
  1. Does "SP2 Cumulative Update #3" include the fix for "Security Bulletin MS16-136 (CU)" ?

    If SP2 CU3 does fix the problem then how do you verify that? Because looking at the KB for "SP2 Cumulative Update #3" it doesn't mention any of the KBs mentioned in MS16-136 (e.g. KB3199641 or KB3194718).

    Also, If it does fix the problem, does this mean this fix is a non-public fix?


    1. Yes, subsequent builds are cumulative, meaning they include all of the fixes from lower builds (occasionally there are discrepancies around service pack time due to code check-in/cut-off time, but in the new model service packs don't exist anymore anyway).

      They aren't listed in later cumulative update KB articles because the KB articles are meant to indicate which new fixes were introduced in that update. If they included all the previous fixes, those articles would become unwieldy very quickly.

  2. Aaron, firstly thank you for maintaining these pages as they are invaluable to me (and I'm sure many others).

    I just wondered if it is worth including a note against SP1/CU9 and SP2/CU2 to call out the following KB:

    Symptoms – Assume that you have installed a cumulative update on an instance of Microsoft SQL Server 2014 that has a service pack installed. When you uninstall the cumulative update and the service pack, none of them are uninstalled correctly. But you don't receive any error messages about this.

    This is fixed in SP1/CU9 and SP2/CU2 so worth highlighting I thought.

  3. Does SQL Server 2014 SP1 CU 10 contain the security patch MS16-136 12.0.4487? Or do we need to apply both CU 10 and 12.0.4487 separately? We are on SP1 with no CU. MS16-136 GDR 12.0.4232 was applied and we were unable to connect to SQL Server. Once we rolled back that patch, everything is fine. We are now considering to apply CUs as per recommendations from MS. We are hoping to confirm that apply CU 10 will include the security patch as well.

    1. Yes, the fixes for MS16-136 should be in CU 10 (I am not sure why they neglect to put this information into the CU KB, but it has been common).

      That said, there is no harm, technically, in applying both patches.

  4. I cannot seem to be able to install SQL Server 2014 SP2 on a Windows Server 2012 machine with 2014 SP1 CU7 installed. When I need to select the instances to updated, all checkboxes are grayed out and I get the error message "There are no SQL Server instances or shared features that can be updated on this computer".

    Anybody confirms this ? Thanks

    1. Hmm, that did not happen to me, can you show what the instance selection screen looks like? There may be a hint in the table at the bottom that shows the existing instances and their versions.

      1. In fact, the problem was I was trying to install an English SP2 over a French SQL Server. No problem once I downloaded the correct file :)

    1. Thanks, you'll notice I maintain two counts, the first is the official number of fixes in the CU according to Microsoft, the second is the count of publicly visible fixes on the CU article itself (minus things like the @@VERSION/SERVERPROPERTY thing they keep including as a "fix" in every CU). I suspect the KB you're pointing out is counted in the former but not the latter.

  5. So my assumption was right, there was something wrong with SP1-CU6. I started from scratch and just installed RTM again. Now planning to SP1 and then cu6 after some days.

  6. Hi
    I installed SP1 CU6 and after then query on clustered column store started running forever.
    A query on table with 0.4 million rows takes 5 mins which was taking few seconds in RTM or SP1.
    Seems some serious issue with SP1 CU6 to handle clustered columnstore index.

    1. Can you let it finish and collect an actual plan, and compare that to an actual plan for the faster version (assuming you still have RTM or SP1 somewhere, which I hope so, because you are not performing these tests for the first time in production, right)? Did you look at wait stats? Where is the 5 minutes being spent?

  7. Hi All. Thanks for the Great Info!
    I applied SQL 2014 SP1 CU5 and it failed with
    "Script level upgrade for database 'master' failed because upgrade step 'SSIS_hotfix_install.sql' encountered error 3906, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion."
    This occurred on 2 Virtual servers in WSFC and AlwaysOn conf. Had to rebuild Master DB since could not restore due to now different version.
    Same CU5 worked fine on 2 other SQL 2014 SP1 CU3 servers. Any thoughts or has anyone else experienced this?

      1. Thanks Aaron, That looks EXACTLY like the issue I experienced. Wish I had that recovery process before I rebuilt the Master DB.
        I'll see if I can reproduce.

  8. After installing SQL Server 2014 SP1 CU3( I Noticed Microsoft updated the download link, there is a "latest" link, I have downloaded the latest setup file from there) on our test environment, nearly all instances' SQL Server agent failed to start, I tried to reboot the server but no help, finally I modified the the following Key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\SQLServerAgent
    Modify the value data of the serverhost key to np:Virtualservername

    Value: np:Virtualservername.

    This will force the SQLServer agent to connect with SQLserver using Named Pipes so
    delegation is not used.

    It looks like this bug:

    Anyone experience the same problem?

  9. At least you guys are able to download the hotfix – I've been getting 404 errors when trying to download this CU's bits from the link MS emails you when you request the hotfix (487890_intl_x64_zip.exe). And based on similar complaints from a few others on MS's blog entry for this CU, apparently I'm not the only one.

  10. Hello Aaron,
    I installed SQL Server 2014 SP1 CU3, below is the output of "select @@version", but my version is different as the version number "12.0.4425" mentioned above, I did checked it yesterday on microsoft webiste, it is""12.0.4425.19", any ideas?

    Microsoft SQL Server 2014 (SP1-CU3) (KB3094221) – 12.0.4427.24 (X64)
    Oct 10 2015 17:18:26
    Copyright (c) Microsoft Corporation
    Developer Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)

  11. Should this: Recommendation: If you are using Analysis Services, or need to stripstream a deployment to multiple servers, apply SP2 Cumulative Update #2 instead.
    Not be instead: Recommendation: If you are using Analysis Services, or need to stripstream a deployment to multiple servers, apply SP1 Cumulative Update #2 instead.

  12. Aaron,

    Just a follow-up. SP1 still fails an installation if I don't detach SSISDB first. I tried your steps, but they don't help. The T902 flag helps start sql, but that is it. Once the flag is removed sql won't start.

    It complains about not being able to find the 'ISSERVER' assembly. I tried to manually add the assembly, remove ssisdb, replace ssisdb, etc. all fail.

    It seems MSFT has another bug.

    1. Yeah I wouldn't expect this latest update to fix that – again, you should initiate a support ticket. If it is indeed a bug (and it sounds like it), the support ticket won't cost you anything, and you'll likely get a fix far sooner than CU #2.

  13. Hello,

    Is it advisable to install SP1 CU1 after having installed RTM CU8?

    I'm afraid that, for many of us, it's not clear which path, RTM o SP1, should be taken.

    Many thanks

    1. SP1 CU1 catches up to all of the fixes in RTM CU8, so yes, my recommendation would be to move to the SP1 branch as soon as your regression testing schedules allow (don't just do it blindly).

  14. Hi Aaron,

    I just recently installed 2014 SP1 Cumulative Update #1 (12.0.4416) to my development workstation and one TEST server. Analysis Services (SSAS) continues to report itself as build 12.0.4100.1 (which is only SP1) and not build 12.0.4416.0. Given that there are quite a few SSAS fixes in this update, this doesn't seem to be right. When I look at the file information for CU #8 (, I see a whole host of SSAS file updates that I do not see in CU 1 for Service Pack 1. From my outside-of-Microsoft perspective, it seems that the SSAS updates were not included in the SP1 branch update as advertised.

    Any insights or can anyone corroborate?

    Thanks in advance!

    1. Hi John, I'm not sure, did you check the setup logs? It sounds to me like the CU was applied only to the database engine and not to the SSAS instance. This has happened to me in the past too, where either the SSAS checkbox was unchecked or I inadvertently unchecked it without noticing.

      1. Hi Aaron,

        The setup logs show that SSAS was detected as an installed product, but there were definitely no actions applied to it (no "sql_as_Cpu64.log" file. I ran the cum. update installer several time to check that I had indeed selected SSAS in the feature tree. I am pretty convinced that the Microsoft SQL team left these out of the cumulative update. Guess I will need to open up a case with Premier Support.

        1. Yeah, sounds like support will be your best bet. If there is an issue, I am sure it will be corrected in CU #2 (which may come out of band, earlier than expected, due to a couple of other issues, such as slipstream not working with SP1).

  15. Correct, it has happened with CU6, CU7 and CU8.
    We don't have anything special in our SSISDB configuration.
    If I get in that position again I will try your solution.

  16. Just a word of caution with SQL 2014 CU6-8.
    I still get an error when the SSISDB is present. This results in the instance being corrupted. I had to reinstall SQL 2014, ensure the SSISDB is not attached and then do the updates. Then when updates are complete re-attach the ssisdb.

      1. I didn't try your solution. My error was very different:

        2015-06-23 10:53:58.89 spid7s Assembly 'ISSERVER' was not found in the SQL catalog of database 'SSISDB'.
        2015-06-23 10:53:58.89 spid7s The failed batch of t-sql statements :

        CREATE FUNCTION [internal].[is_valid_name]
        @object_name NVARCHAR(MAX)
        EXTERNAL NAME ISSERVER.[Microsoft.SqlServer.IntegrationServices.Server.ServerApi].IsValidName

        2015-06-23 10:53:58.89 spid7s Error: 912, Severity: 21, State: 2.
        2015-06-23 10:53:58.89 spid7s Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 6528, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
        2015-06-23 10:53:58.89 spid7s Error: 3417, Severity: 21, State: 3.
        2015-06-23 10:53:58.89 spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
        2015-06-23 10:53:58.89 spid7s SQL Server shutdown has been initiated

        1. Wow, that is a little different, but the warning about "recover the master database" can still be bypassed using the steps I outlined previously (a lot of folks have pressed the panic button, assuming they need to reinstall or completely restore master).

          And that happened with CU8? Nothing special about your SSIS installation except that the SSISDB catalog was in place?

  17. Thanks the updated,

    Is there a reason for CU8? since we can just follow one approach, e.g. upgrade to SP1 then install SP1 CU1 then all done.

    1. Hi Albert, there certainly is. Many people do not move to a service pack the moment it comes out, for a variety of reasons – regression testing, corporate policy, fear-mongering, what have you. Whatever the case may be, you can't just force everyone to move to service pack 1. Microsoft has historically always supported at least the current and previous service pack level, which means that those on the previous branch (in this case RTM) continue to receive security and performance updates, but they implicitly opt out of the feature changes that typically only ship with service packs.

  18. Incorrect Count of Cumulative Update #6
    no. of Cumulative fixes = 339 + 64 = 403 (not 390)
    (public) = 301 +55 = 356 (not 353)

    1. Thanks Ray, nice catch. My math was wrong, but not quite how you describe. The number of updates in CU #6 brings the total to the number of cumulative updates in CU #5 and the number of new updates in CU #6. The latter includes the three hotfixes released in between CU $5 and CU #6 – 403/356 would count those twice.

    1. Hi everyone,

      Just bought a SQL Server 2014 Developer Edition on Amazon and installing it now. I see there is a SP1, SP1 Cumulative Update #1, and SP1 Cumulative Update #2. I also see that there is Update 9 for SQL Server 2014 here: /team-posts/latest-builds-sql-server-2014/ . The prerequisite for Update 9 is SP1. What is the proper order to install this on my PC?

      Is it:

      SQL Server 2014 Dev Edition
      SP1 CU1
      SP1 CU2


      SQL Server 2014 Dev Edition
      Update 9?

      Thanks guys

      1. Cumulative Update #9 is only for the RTM branch; you can't apply it to SP1. Where do you see that the prerequisite for update 9 is SP1?

        You should install: 2014, then SP1, then SP1 CU2. Cumulative updates are, as they're named, cumulative – so there is no need to apply SP1 CU1 before applying SP1 CU2.