Cumulative Update #5 is available for SQL Server 2012 RTM

Microsoft has released Cumulative Update #5 for SQL Server 2012 RTM. Note this is *not* a cumulative update for Service Pack 1. So if your build # is >= 11.0.3000, you should not be installing this update.

  • KB Article: KB #2777772
  • Build # 11.0.2395
  • 28 fixes at the time of writing

Looking for an update for the Service Pack 1 branch? You'll find that in January. For now at least, unlike the SQL Server 2008 R2 SP1/SP2 branches (which are in sync), the release cycles for SQL Server 2012 CUs will alternate – RTM one month, SP1 the next. This is mainly due to the out-of-band release of SP1 CU1 to get it caught up the the RTM CUs.

This update is only relevant for builds 11.0.2100 -> 11.0.3329. Do not attempt to install on SQL Server 2012 SP1 (any build >= 11.0.3000) or any previous version of SQL Server.

Aaron Bertrand

I am a passionate technologist with industry experience dating back to Classic ASP and SQL Server 6.5. I am a long-time Microsoft MVP, write at Simple Talk, SQLPerformance, and MSSQLTips, and have had the honor of speaking at more conferences than I can remember. In non-tech life, I am a father of two, a huge hockey and football fan, and my pronouns are he/him. If I've helped you out, consider thanking me with a coffee. :-)

8 Responses

  1. Ashish Das says:

    Hi Aaron,
    Thanks for reply. I was confused between cumulative update for sql server and cumulative update for service pack. Currently the latest cumulative update for service pack 1 is cumulative 3 . I am going to install it in our server. Hope it will fix the memory issue. I have one more question.
    We have 4 different sql server 2012 box and we are getting issue in almost every box. So we are thinking that sql 2012 is not a stable version yet. What is ur answer to this?

  2. AaronBertrand says:

    Ashish, you can't install RTM CU5 on SP1. Just because there are newer fixes there, it is simply not possible to apply the fix – it will be blocked. Date of release is irrelevant; *branch* is important. You need to wait for the same fix to appear in a CU for the SP1 branch. In this case the fix appears in CU2 for SP1:
    Andrew, in some cases the timing is just off. CU2 for SP1 is "later" than CU5 for RTM, but fixes don't always make it into each branch for various reasons. (I won't speak on behalf of the dev team, but to put it simply, can you always wash both of your cars on the same day, or watch two or three episodes of your favorite show that you DVR'd? There isn't always time to complete tasks according to some optimal schedule.
    Please, everyone, stop assuming that *date* has anything to do with whether a fix is or is not included in any specific CU. Check the fix list for the CU to find your fix, or watch the individual KB for updates. If you're not seeing a fix for your branch that is in another one, contact CSS. *I* certainly can't do anything about it.

  3. Ashish Das says:

    @Aaron : We are getting memory leak\pressure issue in our sql server 2012. The hotfix no. is We have already installed service pack1 and I think we need to install CU5. Please let me know..

  4. Ashish Das says:

    You said " Do not attempt to install on SQL Server 2012 SP1 (any build >= 11.0.3000) or any previous version of SQL Server.". That's why I am saying you are wrong because there are some fixes which are there in CU5 not in SP1.

  5. Aaron Bertrand says:

    Ashish, what are you talking about?

  6. Ashish Das says:

    You are wrong Mr Aaron. SP1 is released in Nov 2012 and CU 5 is in dec 2012.

  7. Andrew says:

    Seeing as you seem to know a little about the machinations of the release strategy, can you answer this 🙂 ???
    RTM CU5 has a fix for bug 2764343.  Since it was released in December 2012, there's been a CU2 update released for SQL 2012 SP1 in January 2013 (as you foreshadowed). How does the bug fix for 2764343 manage to be included in RTM CU5 (earlier) and *not* SP1 CU2 (later)?
    It seems a little odd to be faced with a choice of applying a more recent update which won't fix the bug and an older one which will!

  8. An says:

    What is cu for 2012 sp1