THE SQL Server Blog Spot on the Web
Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search
Home Blogs Downloads   Opml View as RSS news feed in XML

Aaron Bertrand

Aaron is a senior consultant for SQL Sentry, Inc., makers of performance monitoring and event management software for SQL Server, Analysis Services, and Windows. He has been blogging here at sqlblog.com since 2006, focusing on manageability, performance, and new features; has been a Microsoft MVP since 1997; tweets as @AaronBertrand; and speaks frequently at user group meetings and SQL Saturday events.

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.

Published Monday, December 17, 2012 11:44 PM by AaronBertrand

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

An said:

What is cu for 2012 sp1

December 23, 2012 3:58 AM
 

Andrew said:

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!

February 7, 2013 11:55 PM

Leave a Comment

(required) 
(required) 
Submit

About AaronBertrand

...about me...

This Blog

Syndication
©2006-2012 SQLblog.comTM
Brought to you by Adam Machanic & Peter DeBetta
Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement