Search results matching tag 'SP2'

April 2013 Cumulative Updates for SQL Server 2008 R2

AaronBertrand — Mon, 15 Apr 2013 18:00:00 GMT

Today Microsoft released new cumulative updates for SQL Server 2008 R2.

SQL Server 2008 R2 Service Pack 1 Cumulative Update # 12

KB Article: KB #2828727
7 fixes listed at time of publication
Build number is 10.50.2874
Relevant for @@VERSION 10.50.2500 through 10.50.2873

SQL Server 2008 R2 Service Pack 2 Cumulative Update # 6

KB Article: KB #2830140
13 fixes listed at time of publication
Build number is 10.50.4279
Relevant for @@VERSION 10.50.4000 through 10.50.4278

My usual disclaimer: these updates are NOT for SQL Server 2008 (or SQL Server 2012). Only apply to systems where SELECT @@VERSION returns 10.50.xxxx, where xxxx is >= 2500. If xxxx < 2500, you need to start thinking about getting off the RTM branch. And based on the number of fixes making it into the SP2 updates, you might consider abandoning SP1, too, if possible...

SQL Server 2008 R2 Service Pack 2 Cumulative Update #1 is available

AaronBertrand — Wed, 01 Aug 2012 19:23:00 GMT

Microsoft has released a cumulative update for SQL Server 2008 R2 SP2, which was only released last week.

KB article is http://support.microsoft.com/kb/2720425
Build number is 10.50.4260.0
There are 35 fixes published as of 2012-08-01
This update is relevant for builds between 10.50.4000 and 10.50.4259

My recommendation: if you have already installed Service Pack 2, or were waiting on the first cumulative update before doing so, this may be what you've been waiting for. According to the SQL Release Services Blog, SP2 CU#1 includes all of the fixes from SP1 CU#6 and CU#7 (which were not included in SP2 RTM).

My usual disclaimer: these updates are NOT for SQL Server 2008. Only apply to systems where @@VERSION returns 10.50.xxxx, where xxxx is >= 4000.

SQL Server 2008 R2 Service Pack 2 CTP is available

AaronBertrand — Mon, 14 May 2012 18:23:00 GMT

You can download the Service Pack 2 CTP from the following URL:

http://www.microsoft.com/en-us/download/details.aspx?id=29848

The build # is 10.50.3720. This service pack contains all of the fixes from Service Pack 1 & Cumulative Updates 1 through 5, and a couple of other minor fixes (a couple of SSRS bugs and a bug about an ALTER TABLE batch not being cached correctly). It does not include fixes from Service Pack 1 Cumulative Update #6, which I mentioned recently.

You should *NOT* install this service pack preview if:

your build number (SELECT @@VERSION;) is 10.00.xxxx (since this is SQL Server 2008, not SQL Server 2008 R2);
your build number is >= 10.50.1815 and < 10.50.2500 (since you may be undoing fixes you are using from RTM CU13); or,
your build number is >= 10.50.2811 (since you will be undoing fixes you might be using from SP1 CU6).

SQL Server 2005 : Comparing SP2 CU#12 and SP3 CU#2

AaronBertrand — Sat, 21 Feb 2009 00:49:00 GMT

The recent release of security fixes for SQL Server 2000 and 2005 (the issue did not impact SQL Server 2008) announced in MS09-004 seemed to spur two SQL Server 2005 cumulative updates (CUs) earlier this week -- one for those on SP2, and one for those on SP3. (This typically happens when there is a new service pack released, as adoption rates are not always very fast, and the previous service pack is usually supported for some time.)

But as colleagues noted, the KB articles for the two releases may lead you to believe that there are fixes in CU12 that are not in CU2, and vice versa. And in fact this is true. So a few people have been wondering if they should upgrade to SP3 + CU2, or if doing so will leave them vulnerable to a fix that is only in SP2 + CU12 (or vice versa - a vintage Clash hit comes to mind). In case you were wondering which fixes you have depending on which "branch" you are on, here is the list I took from the two KB articles:

	SP2 CU # 12 (9.00.3315)	SP3 CU # 2 (9.00.4211)
960971	no	yes
960977	no	yes
961123	yes	no
961146	no	yes
961237	yes	no
961396	yes	no
961479	yes	yes
961648	yes	yes
961739	yes	no
961920	no	yes
961935	no	yes
962003	no	yes
962209	yes	yes
963684	no	yes
967164	no	yes
967169	yes	no
967180	no	yes
967192	yes	no
967316	yes	no
967527	yes	no
967570	yes	no
967618	yes	no
967625	yes	no

(FWIW, I tried to highlight the three rows where the fix is included in both CUs, but Community Server is having none of it. The software either butchers whatever attributes I try to add, or strips them entirely. Hopefully bold is enough, but if not, they are KB #s 961479, 961648, and 962209.)

A contact at Microsoft explained that a specific customer hotfix request for one version (e.g. SP2) may not get ported immediately to another service pack (or another version). The initial goal is to provide the fix for that customer's version, unless requests come in for more than one version. After that, the fix will make it into other relevant branches as time allows (in most cases they try to accomplish this by the next CU if they can't get in by the current cycle's deadline). This process makes sense, of course, I just don't think it's very visible. A lot of people assume that hotfixes that come out at the same time will contain the same set of fixes. That assumption makes sense too, and while it is surely the goal, it just can't always happen.

He also promised an authoritative list of fixes for the two CUs, and if it differs from the above, I will post an update here.