Latest Builds of SQL Server 2014

Updated June 22, 2016

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 1 Branch

The official knowledge base article for Service Pack 1 has been moved to KB #3058865, and you can download it here. The original blog posts are here and here; the new one is here.

Service Pack 1 includes a number of enhancements; these were the most interesting to us:

  • The behavior of trace flags 1236 (see KB #2926217) and 9024 (see KB #2809338) will now be enabled by default.

  • Several fixes for buffer pool extensions, including the ability to use instant file initialization.
  • Improvements in columnstore performance and new extended event coverage for columnstore inserts.

Build Name Build # KB Article Date New fixes (public)
SP1 Cumulative Update #7 12.0.4459 KB #3162659 2016-06-20 35 (32)
This Cumulative Update includes a fix that is currently not mentioned in the list of fixes (but that should be rectified soon): KB #3166902 : FIX: logs are missing after multiple failovers in a SQL Server 2014 failover cluster. Kendra Little blogged about this fix.
SP1 Cumulative Update #6
12.0.4457 KB #3167392 2016-05-31 44 (43)
This Cumulative Update has 44 fixes, most importantly this fix for corruption after dropping columns and a fix for the NOLOCK regression introduced in the original CU6 release (see KB #3167394 for more details). It also introduces the ability to update multiple statistics on the same table at the same time (see KB #3156157).

Recommendation: Apply the latest Cumulative Update above.

COD Hotfix 3147825 12.0.4452 KB #3147825 2016-04-05 1 (1)
This critical on-demand (COD) hotfix addressed an issue with distributed transaction in Availability Groups, where you can experience assertion failures, stack dumps, and suspect databases. The fix has been replaced by the most recent CU.

Recommendation: Apply the latest Cumulative Update above, which includes this fix. (Right now, the KB article has been taken down anyway.)

SP1 Cumulative Update #6
12.0.4449 KB #3144524 2016-04-18 N/A
Originally, this Cumulative Update introduced a regression which could lead to queries that use NOLOCK / READ UNCOMMITTED to behave as if they were under READ COMMITTED (so they can block and be blocked). If you use this dangerous isolation level all over your code, you'll want the update above. See KB #3167394.

Recommendation: Apply the latest Cumulative Update above.

SP1 Cumulative Update #5 12.0.4439 KB #3130926 2016-02-22 20 (20)
COD Hotfix 3130999 12.0.4437 KB #3130999 2016-02-05 2 (2)
Important: This critical on-demand hotfix brings CU4 customers up-to-date with the two hotfixes mentioned below, KB #3097972 and KB #3119148.

Recommendation: Apply the latest Cumulative Update above.

SP1 Cumulative Update #4 12.0.4436 KB #3106660 2015-12-22 34 (34)
Important: The two COD hotfixes immediately below are *NOT* included in this cumulative update. If you've already installed CU4, you've lost these two updates below, unless you apply Hotfix 3130999 above, or Cumulative Update #5 or greater.

Recommendation: Apply the latest Cumulative Update above.

COD Hotfix 3119148 12.0.4433 KB #3119148 2015-12-09 1 (1)
This critical on-demand hotfix addresses an error message when a network blip occurs while backing up to Azure.

Recommendation: Apply the latest Cumulative Update above.

COD Hotfix 3097972 12.0.4432 KB #3097972 2015-11-19 3 (3)
This critical on-demand hotfix addresses three issues: (1) linked server errors; (2) out of memory errors; and, (3) access violations when using TDE or BPE.

Recommendation: Apply the latest Cumulative Update above.

SP1 Cumulative Update #3 12.0.4427 KB #3094221 2015-10-19 40 (36)
SP1 Cumulative Update #2 12.0.4422 KB #3075950 2015-08-17 51 (46)
COD Hotfix 3078973 12.0.4419 KB #3078973 2015-07-24 13 (13)
This critical on-demand hotfix addressed two primary issues (and 11 others): (1) CU1 was not capable of slipstream, and (2) SSAS was not properly targeted for CU1 updates.

Recommendation: Use the latest CU above; these fixes are all included.

SP1 Cumulative Update #1 12.0.4416 KB #3067839 2015-06-22 141 (121)
SP1 Cumulative Update #1 includes 141 fixes, including all of the fixes from the RTM Cumulative Updates published up to and after SP1 was released (CU #6, CU #7, and CU #8 – see this post for confirmation if you don't want to cross-reference all those fixes manually). One of the more important fixes is one that involves partial (and thus incorrect) results from a clustered columnstore index with a corrupted rowgroup (more gory details in this blog post and KB #3067257).

However, issues were discovered shortly after release: The Analysis Services fixes documented in the KB aren't actually included (in fact SSAS is not touched at all), and slipstreaming RTM+SP1+CU1 was not possible. There is a fix available, but a more recent cumulative update is by far the better play now.

CU #1 also includes TLS 1.2 support (see KB #3135244, KB #3052404, and the Release Services blog for more details). However, there is a known issue described in KB #3135852 that means you should apply the latest Cumulative Update instead. See this post for more details.

Recommendation: Apply the latest Cumulative Update above.

SP1 GDR TLS 1.2 Update 12.0.4219 KB #3098852 2016-01-29 2 (2)
Includes TLS 1.2 support (see KB #3135244 and the Release Services blog for more details).
COD Hotfix 3070446 12.0.4213 KB #3067257 2015-05-15 1 (1)
This GDR update addresses an issue described in KB #3067257: a wrong results bug with Columnstore indexes. I suspect they issued this GDR so that they could release this fix while they continue to work out the snafu with Cumulative Update #1, mentioned above. The update may already be being pushed to you via Microsoft Update.

Recommendation: Install this GDR if you have been holding out on CUs and @@VERSION >= 4000 and < 4213. Most people should opt for the latest cumulative update instead.

Service Pack 1 12.0.4100 KB #3058865 2015-05-15 29 (29)
Service Pack 1 (initial) 12.0.4050 This release was pulled from distribution shortly after release.

RTM Branch

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 SP1 branch soon anyway.)

Comments ( 45 )

                                  • Cumulative Updates – SQL Server 2014 RTM CU3 | phoebix says:

                                    […] there is a security update I strongly urge you to consider installing on any servers. This post here sums it up […]

                                  • Mikhail says:

                                    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: . 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

                                  • Aaron Bertrand says:

                                    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.

                                  • Ray says:

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

                                  • Aaron Bertrand says:

                                    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.

                                  • Albert says:

                                    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.

                                  • Aaron Bertrand says:

                                    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.

                                  • Jeff says:

                                    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.

                                  • Aaron Bertrand says:

                                    Hi Jeff, did you see the notes I posted here? You shouldn't have had to reinstall SQL Server.

                                  • Jeff says:

                                    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)
                                    RETURNS BIT
                                    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

                                  • Aaron Bertrand says:

                                    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?

                                  • Jeff says:

                                    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.

                                  • John B. says:

                                    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!

                                  • Aaron Bertrand says:

                                    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.

                                  • John B. says:

                                    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.

                                  • Aaron Bertrand says:

                                    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).

                                  • John B. says:

                                    Thanks Aaron. Late yesterday (7/8/2015), Microsoft confirmed my issue and your prediction above in an update message on the bottom of their blog post announcing this CU –> .

                                  • Félix F. says:


                                    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

                                  • Aaron Bertrand says:

                                    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).

                                  • Félix F. says:

                                    Many thanks for your fast answer!

                                  • Jeff says:


                                    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.

                                  • Aaron Bertrand says:

                                    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.

                                  • ErikEJ says:

                                    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.

                                  • Aaron Bertrand says:

                                    Yes, silly typo, thanks

                                  • Albert says:

                                    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)

                                  • Aaron Bertrand says:

                                    Yes, the original KB article (and in fact the build I originally downloaded) showed 4425. Now the source KB article says 4427, but others still say 4425 (e.g. this one and this one.

                                  • Tom S. says:

                                    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.

                                  • Aaron Bertrand says:

                                    Yes, I am getting a 404 now, but I was able to download it at the time. If I request a new hotfix download for x64 CU3, I get a different link than the previous e-mail I had received:


                                  • Patrick Clough says:

                                    Any update on being able to correctly download CU3? I tried today and get sent this link.


                                  • Aaron Bertrand says:

                                    Hi Patrick, I clicked on that link and it downloaded fine…

                                  • Albert says:

                                    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

                                    Ie:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
                                    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?

                                  • Cumulative Updates – SQL Server 2014 SP1 CU4 | Phoebix says:

                                    […] that two COD releases post-CU3 are not included in this update. The full info can be read on the SQL Sentry site, which covers the updates for both SP1 and RTM releases in SQL Server than I do in my […]

                                  • Jeff Humphreys says:

                                    12.0.4437 is available; it now includes COD Hotfix 3119148 and COD Hotfix 3097972.

                                  • Aaron Bertrand says:

                                    Thanks Jeff, I think I'm all caught up.

                                  • Gregor says:

                                    Hey, i just successfully installed kb3130999 over a SQL 2014 SP1 Installation (12.0.4213.0) – without CU4.

                                    But describes:

                                    To apply this hotfix package, you must have SQL Server 2014 SP1 CU4 installed on your computer.

                                    So iam confused..

                                  • Aaron Bertrand says:

                                    That's a mistake, and it will get cleaned up. The hotfix is cumulative and does not require CU4 to already be installed.

                                  • Aaron Bertrand says:

                                    Hi Gregor, the wording in the KB article has been corrected:

                                    To apply this hotfix package, you must have SQL Server 2014 SP1 installed on your computer.
                                  • Bill Fritz says:

                                    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?

                                  • Aaron Bertrand says:

                                    Huh, that issue sounds awfully familiar to something that happened with SP1 (scroll up and see this and this). As I suggested above, I would contact support.

                                  • Bill Fritz says:

                                    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.

                                  • Amish says:

                                    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.

                                  • Aaron Bertrand says:

                                    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?

                                  • Amish says:

                                    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.

                                  • Chris Wood says:

                                    You might want to change your count for SP1 CU7 as Kendra Little found this which references CU7 but isn't in the actual list of fixes.

                                  • Aaron Bertrand says:

                                    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.

                                  Leave A Comment

                                  Your email address will not be published.