THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Aaron Bertrand

Aaron is a Product Evangelist for SentryOne, makers of Plan Explorer and a performance monitoring and event management platform for the Microsoft Data Platform and VMware. He has been blogging here at since 2006, focusing on manageability, performance, and new features, and also blogs at and; has been a Microsoft MVP since 1997; tweets as @AaronBertrand; and speaks frequently at major conferences, user group meetings, and SQL Saturday events worldwide.

SQL Server 2014 Cumulative Update #7 is available!

Microsoft has released Cumulative Update #7 for SQL Server 2014. See this blog post for more information.

  • KB Article: KB #3046038
  • 41 fixes listed publicly at time of publication (47 total)
  • Build number is 12.0.2495 
  • Relevant for @@VERSION 12.0.2000 through 12.0.2494 
Note: This cumulative update is only for RTM - do not attempt to install if you have already deployed Service Pack 1.
Published Thursday, April 23, 2015 10:08 AM by AaronBertrand



Grzegorz Łyp said:

Will this CU be included in the fixed SP1 for SQL 2014 ?

April 23, 2015 11:27 AM

AaronBertrand said:

Grzegorz I don't know for certain, but it is unlikely that CU6 or CU7 will be in the updated SP1. They need to focus on testing the bits they have. For all prior service packs, the last CU (or sometimes 2) will be included in a quick, post-SP CU. So you should get all the CU6/CU7 fixes in SP1 CU1, and it will probably be released within a few weeks of the re-released service pack. However, that is just my opinion based on past events. After this debacle it might be the right time for them to commit to spending a lot more time testing CUs and SPs before they release them.

April 23, 2015 11:52 AM

cinahcaM madA said:

I would agree that this will likely not be included in the SP.

And I would add that this is where it gets super-annoying trying to figure out what to do, especially in an enterprise setting where standardization is important. There are a few very important-looking fixes here. I don't see any clear way for a DBA to know which build will provide a better experience, aside from extensive testing of everything that gets released... I hope Microsoft will go back to a single-path methodology.

April 24, 2015 11:23 AM
New Comments to this post are disabled

About AaronBertrand

...about me...

This Blog



Privacy Statement