SentryOne Team Blog (

Latest Builds of SQL Server 2012

Below you will find the most recent builds for SQL Server 2012 – RTM, Service Pack 1, Service Pack 2, Service Pack 3, and Service Pack 4. As always, please be sure to perform full regression testing before deploying any builds (including service packs) to production instances. Kendra Little has a nice post about this.

In addition to trying to stay on the most recent releases in order to have the most recent fixes and enhancements, be sure to check out this CSS blog post and KB #2964518 : Recommended updates and configuration options for SQL Server 2012 and SQL Server 2014 used with high-performance workloads, which is full of useful advice.

Service Pack 4

Service Pack 4 will be the last service pack for SQL Server 2012, released on October 5th, 2017. It contains all fixes up to and including Service Pack 3 Cumulative Update #10, and is pretty . This is pretty much the end of the line for servicing of SQL Server 2012 outside of critical bugs and security fixes, so now really might be the time to start thinking about moving to something more modern.

Build Name Build # KB Article Date New Fixes (public)
COD Hotfix for SQL Server 2012 SP4 11.0.7469.6 KB #4091266 2018-03-28 2 (2)
Security Advisory
ADV180002 (GDR)
   11.0.7462.6     KB #4057116  2018-01-12 1 (1)

In case you haven't heard, there are major processor-related password theft vulnerabilities hitting the news: Meltdown and Spectre. Microsoft has guidance for many versions of SQL Server here:

There are fixes for all versions of SQL Server that are still in support, and even a few that are long out of support (I'm looking at you, SQL Server 2008 & 2008 R2). This is great, but keep in mind, in most cases, you'll need to be on the most recent service pack to get patched. So if you're on, say, 2012 SP2 or 2014 RTM, you may have an upgrade in your near future.

There is also a guidance article for Windows:

And there may be more to it than that for you, depending on whether you are on shared VMs, have specific types of workloads, or have additional vulnerability due to things like CLR. I won't go into heavy weeds here (perhaps the subject of a separate, independent post), but others have already gone into great detail. Here are some terrific starters, even though The Register incorrectly implies in the first headline that only Intel is affected:

Microsoft has also published some more detail and guidance about the issue:

This is pretty serious stuff, but you need to be aware that at this point the impact of the patch to performance of SQL Server workloads is unknown, and could be significant. Currently the Windows Server guidance piece documents a registry update you can make to stop the effects of the patch, but if you do this, you should definitely have other mitigation plans.

You may have issues applying the patches if you are using anti-virus software (see this article from Microsoft).

These vulnerabilities reach well beyond SQL Server. A recent piece over at Tom's Hardware shows that these exploits can happen through your web browser, too. So maybe you should leave this page and just unplug your ethernet cable until someone gives you a smoke signal that patches are available for all platforms and devices.

Service Pack 4 11.0.7001.0 KB #4018073 2017-10-05 23 (23)
Service Pack 3

Service Pack 3 was first made available on November 22, 2015; you can download it here and read more at the following sites:

The most interesting fixes in SP3, at least to me, are:

But probably the best thing about this service pack? Unlike most service packs, this one includes all of the fixes from the latest cumulative update on the preceding branch at the time of release (so everything from 2012 SP2 CU9, but not CU10 or later).

The download page for SQL Server 2012 SP3 Cumulative Updates always has the latest CU. If you need an earlier CU, you can usually find it in the Microsoft Update Catalog, though the list changes depending on your search terms.

Build Name Build # KB Article Date New Fixes (public)
Security Advisory
ADV180002 (CU)
   11.0.6615.2    KB #4057121    2018-01-16    1 (1)
Please see the Spectre/Meltdown blurb above for more details.
SP3 Cumulative Update #10
11.0.6607.3 KB #4025925 2017-08-08 5 (5)
SP3 Cumulative Update #9 11.0.6598 KB #4016762 2017-05-15 12 (10)
SP3 Cumulative Update #8 11.0.6594 KB #4013104 2017-03-21 17 (17)
SP3 Cumulative Update #7 11.0.6579 KB #3205051 2017-01-18 12 (12)
SP3 Cumulative Update #6
Security Bulletin MS16-136 (CU)
KB #3194724
11.0.6567 KB #3194992 2016-11-17 16 (11)
SP3 Cumulative Update #5 11.0.6544 KB #3180915 2016-09-20 21 (18)
KB #3162589 alone makes this Cumulative Update worth it. Without the update, you could observe super-latches with virtually exponential growth in worker time (otherwise fixed only by a restart).
SP3 Cumulative Update #4 11.0.6540 KB #3165264 2016-07-18 23 (22)
SP3 Cumulative Update #3 11.0.6537 KB #3152635 2016-05-17 21 (21)
SP3 Cumulative Update #2 11.0.6523 KB #3137746 2016-03-22 21 (19)
SP3 Cumulative Update #1 11.0.6518 KB #3123299 2016-01-20 8 (8)
SP3 GDR builds below – for non-CU path
Security Advisory
ADV180002 (GDR)
   11.0.6260.1    KB #4057115    2018-01-16    1 (1)
Please see the Spectre/Meltdown blurb above for more details.
Security Bulletin MS16-136 (GDR)
KB #3194721
11.0.6248 KB #3194721 2016-11-08 1 (1)
SP3 GDR TLS 1.2 Update 11.0.6216 KB #3125246 2016-01-29 1 (1)
Includes TLS 1.2 support (see KB #3135244 and the Release Services blog for more details).
Service Pack 3 11.0.6020 KB #3072779 2015-11-22 37 (37)

For official information about SQL Server 2012 builds released after Service Pack 3, see KB #3133750. The latest Cumulative Update will always be available at this download page. If you need any of the earlier Cumulative Updates, you'll need to get them from the Microsoft Update Catalog (see Jonathan Kehayias' post about this here).

Service Pack 2 (RETIRED)
Service Pack 1 (RETIRED)

New call-to-action

29 replies on “Latest Builds of SQL Server 2012”

29 Comments (Comments are now closed.)
  1. After installing on a fresh 2012sp4 (without Security Advisory ADV180002 (GDR)) the product version of sqlservr.exe in C:\Program Files\Microsoft SQL Server\MSSQL11.SQL2012STD\MSSQL\Binn\ is 11.0.7469.6 , file has date 01.03.2018 04:25 file version says 2011.110.7469.6
    select @@version returns "Microsoft SQL Server 2012 (SP4-OD) (KB4091266) – 11.0.7469.6 (X64) Feb 28 2018 17:47:20 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) "
    select SERVERPROPERTY('ProductVersion') returns "11.0.7469.6"

  2. Hello,

    This is a great document. I'm a newbie to SQL so a few questions and please excuse my ignorance. According to the SELECT@@VERSION, my current version is 11.0.3156 , which translates to SQL Server 2012 Service Pack 1 and 64 bit. So from what I read is this the preferred upgrade path? (Currently) SQL Server 2012 Service Pack 1 > upgrade to Service Pack 1 CU16 > Then install Service Pack 2 > Then install Service Pack 2 CU2 > Then install Service Pack 2 CU16 > then upgrade to SQL Server 2012 Service Pack 3. Any help is appreciated. Thanks Reez

    1. Hi @Reezie, no you don't have to do all of that. Both Service Packs and Cumulative Updates are cumulative. All you need to install is Service Pack 3 (and the latest SP3 CU in my opinion); all those steps in the middle would just be wasteful.

    1. Yes, I believe it is safe; I thought I made that clear. Of course, there is always some level of risk in *any* upgrade, no matter how minor, so please do this in a test environment first.

  3. Arron, We want to apply SQL Server Service Pack 2 Cummulative Update 8 after installing service Pack 2, but we still doubt about it, since we got email from microsoft that it's not fully testing yet.. Is it safe?

  4. Running select @@version on my SQL Server 2012 returns:
    Microsoft SQL Server 2012 – 11.0.5343.0 (X64)
    May 4 2015 19:11:32
    Copyright (c) Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) (Hypervisor)

    Build 11.0.5343 would seem to be clearly in the SP2 sequence, but the title still reports SP1. Is there any chance I'm missing some of the earlier fixes? I've requested CU7, but I'd like to know what's going on before I install it.


      1. Can we upgrade SQL server SP1 + CU3 to SQL server SP2 + CU1 without installing SP2 first? and is it better to update to the most recent cummulatives, or just the cummulatives that fixed bugs we find?

  5. Aaron, for this section "•Service Pack 2 (like RTM and SP1) is vulnerable to potential data loss or corruption during online parallel index rebuilds; you should apply Cumulative Update #4" do we have to install CU#4 or CU#1 should provide the fix?

    1. George, I've updated the wording. You can get the fix from CU #1 but if you're going to go to the lengths of installing a Cumulative Update, you may as well install the most recent one (and the necessary hotfix 11.0.5571 if you are using Availability Groups).

    1. Pedro, are you talking about what Windows File Explorer tells you is the version of some individual file, or what Management Studio shows you in Help | About? We're talking about what you get from the following query:


      For SQL Server 2012 SP2, I get this as the first line of output:

      Microsoft SQL Server 2012 - 11.0.5058.0 (X64)

      Also, the instance-level node for a 2012 SP2 server in Management Studio's Object Explorer shows 11.0.5058 beside the name, not 11.2.5058.

      These are the two most common ways people determine their build of the SQL Server engine. This list is meant to compare to @@VERSION output, not looking at file properties or the version of client tools.

      1. Yo are absolutely right. I just came back here to make that correction and you beated me to the punch, ha :)

        It is important to point that out for when looking at the Program and Features in the Control Panel in order to see each components have been updated. This is particularly the issue with the spPowerPivot.msi package, which does not tend to get updated by default.

  6. Thanks for including this, team. It is VERY much appreciated. Keeping things straight with that corruption bug is a freaking pain. Just told a team member to hold off on patching a particular box until CU1