Search results matching tag 'SQL Server 2008 R2'http://sqlblog.com/search/SearchResults.aspx?o=DateDescending&tag=SQL+Server+2008+R2&orTags=0Search results matching tag 'SQL Server 2008 R2'en-USCommunityServer 2.1 SP2 (Build: 61129.1)Out-of-band hotfix releases for SQL Server 2008 SP4 and 2008 R2 SP3http://sqlblog.com/blogs/aaron_bertrand/archive/2015/02/11/out-of-band-hotfix-rollup-for-sql-server-2008-r2-sp3.aspxThu, 12 Feb 2015 02:29:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:57853AaronBertrand<p>Back in September, I blogged about the availability of <a target="_blank" mce_href="http://sqlblog.com/blogs/aaron_bertrand/archive/2014/09/28/sql-server-2008-r2-service-pack-3-is-available.aspx" href="http://sqlblog.com/blogs/aaron_bertrand/archive/2014/09/28/sql-server-2008-r2-service-pack-3-is-available.aspx">SQL Server 2008 R2 Service Pack 3</a>&nbsp;and <a target="_blank" href="http://sqlblog.com/blogs/aaron_bertrand/archive/2014/09/30/sql-server-2008-service-pack-4-is-available.aspx">SQL Server 2008 Service Pack 4</a>. I made it clear that there would be no cumulative updates after those service packs, and while there still hasn't been any such release, Microsoft this week *kind of* made me look like a liar. They have released what they're calling an "on-demand hotfix update" in <a target="_blank" mce_href="http://support.microsoft.com/kb/3033860" href="http://support.microsoft.com/kb/3033860">KB #3033860</a> (2008 R2 SP3) and <a target="_blank" mce_href="http://support.microsoft.com/kb/3034373" href="http://support.microsoft.com/kb/3034373">KB #3034373</a> (2008 SP4).&nbsp;</p>
<p>
While the updates will bring 10.50.6000 up to 10.50.6525 or 10.0.6000 up to 10.0.6526, there is not much to them; only two fixes are listed publicly:&nbsp;</p>
<ul>
<li><a target="_blank" mce_href="http://support.microsoft.com/kb/3027860" href="http://support.microsoft.com/kb/3027860">KB #3027860 : Error 17066 or 17310 during SQL Server startup</a></li>
<li><a target="_blank" mce_href="http://support.microsoft.com/kb/3027857" href="http://support.microsoft.com/kb/3027857">KB #3027857 : FIX: Error 832 occurs after you apply update MS14-044 to SQL Server 2008 R2</a></li>
</ul>
&nbsp;SQL Server 2008 R2 Service Pack 3 is available!http://sqlblog.com/blogs/aaron_bertrand/archive/2014/09/28/sql-server-2008-r2-service-pack-3-is-available.aspxMon, 29 Sep 2014 01:06:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:55480AaronBertrand<p>Microsoft has released a final service pack for SQL Server 2008 R2: Service Pack 3. The build # is 10.50.6000.34 and you can <a target="_blank" mce_href="http://www.microsoft.com/en-us/download/details.aspx?id=44271" href="http://www.microsoft.com/en-us/download/details.aspx?id=44271">download it here</a>. This is essentially a rollup of all of the fixes from the 13 cumulative updates for this branch (if you want to get a complete list of fixes, start at <a target="_blank" mce_href="http://support2.microsoft.com/kb/2730301" href="http://support2.microsoft.com/kb/2730301">KB #2730301</a>). For the fixes specific to SP3, see <a target="_blank" href="http://support2.microsoft.com/kb/2979597">KB #2979597</a>. There are only two issues officially listed in addition to the cumulative update fixes; these include the security fixes from <a target="_blank" href="https://technet.microsoft.com/en-us/library/security/ms14-044.aspx">MS14-044</a> (also see <a target="_blank" href="http://blogs.msdn.com/b/sqlreleaseservices/archive/2014/09/26/sql-server-2008-r2-service-pack-3-has-released.aspx">the Release Services blog post</a>).</p>
<p>There is no independent service pack release for SQL Server 2008 R2 Express; however, you should be able to apply the standard Service Pack 3 against any eligible instance. Also, Service Pack 3 will not be published using Microsoft Update.</p>
<p><b>Important note:</b> this will be the last service release of any kind for SQL Server 2008 R2 (there will be no cumulative updates for SP3). So if you are not moving to 2012 and were waiting for some sign to deploy fixes, this may be it.
</p>
<p><i>My usual disclaimer: this update is NOT for SQL Server 2008 (or SQL Server 2012). Only apply to systems where SELECT @@VERSION returns 10.50.xxxx, where xxxx is &lt; 6000.&nbsp;</i>&nbsp;</p>June 2014 Cumulative Update for SQL Server 2008 R2 SP2http://sqlblog.com/blogs/aaron_bertrand/archive/2014/06/30/june-2014-cumulative-update-for-sql-server-2008-r2-sp2.aspxTue, 01 Jul 2014 03:25:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:54359AaronBertrandMicrosoft has released the final Cumulative Update (#13) for SQL Server 2008 R2 Service Pack 2.
<ul>
<li><span>KB Article: <a target="_blank" mce_href="http://support.microsoft.com/kb/2967540" href="http://support.microsoft.com/kb/2967540">KB #2967540</a></span></li>
<li><span>15 public fixes listed at time of publication (17 fixes total)</span></li>
<li><span>Build number is 10.50.4319</span></li>
<li><span>Relevant for @@VERSION 10.50.4000 through 10.50.4318<br><br></span></li>
</ul>
<div><i>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 &gt;= 4000.&nbsp;</i></div>April 2014 Cumulative Update for SQL Server 2008 R2 SP2http://sqlblog.com/blogs/aaron_bertrand/archive/2014/04/21/april-2014-cumulative-update-for-sql-server-2008-r2-sp2.aspxTue, 22 Apr 2014 00:42:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:53678AaronBertrandMicrosoft has released Cumulative Update #12 for SQL Server 2008 R2 Service Pack 2.
<ul>
<li><span>KB Article: <a target="_blank" mce_href="http://support.microsoft.com/kb/2938478" href="http://support.microsoft.com/kb/2938478">KB #2938478</a></span></li>
<li><span>13 fixes listed at time of publication</span></li>
<li><span>Build number is 10.50.4305</span></li>
<li><span>Relevant for @@VERSION 10.50.4000 through 10.50.4304<br><br></span></li>
</ul>
<div><i>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 &gt;= 4000.&nbsp;</i></div><div>&nbsp;</div>
<b>Important</b>
<p>If you want a final service pack for SQL Server 2008 R2, please comment and vote on these Connect items:</p>
<p>&nbsp; &nbsp;&nbsp;<a target="_blank" href="http://connect.microsoft.com/SQLServer/feedback/details/814658/release-final-service-packs-for-sql-server-2008-and-2008-r2">Connect #814658 : Release Final Service Packs for SQL Server 2008 and 2008 R2</a>
</p>
<p>&nbsp; &nbsp;&nbsp;<a target="_blank" href="http://connect.microsoft.com/SQLServer/feedback/details/814600/release-service-pack-3-for-sql-server-2008-r2">Connect #814600 : Release Service Pack 3 for SQL Server 2008 R2</a></p>
<p><span><i>&nbsp;</i>&nbsp;</span></p>February 2014 Cumulative Update for SQL Server 2008 R2 SP2http://sqlblog.com/blogs/aaron_bertrand/archive/2014/02/19/february-2014-cumulative-update-for-sql-server-2008-r2-sp2.aspxWed, 19 Feb 2014 13:20:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:52871AaronBertrandMicrosoft has released Cumulative Update #11 for SQL Server 2008 R2 Service Pack 2.
<ul>
<li><span>KB Article: <a target="_blank" mce_href="http://support.microsoft.com/kb/2926028" href="http://support.microsoft.com/kb/2926028">KB #2926028</a></span></li>
<li><span>12 fixes listed at time of publication</span></li>
<li><span>Build number is 10.50.4302</span></li>
<li><span>Relevant for @@VERSION 10.50.4000 through 10.50.4301<br><br></span></li>
</ul>
<div><i>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 &gt;= 4000.&nbsp;</i></div><div>&nbsp;</div>
<b>Important</b>
<p>If you want a final service pack for SQL Server 2008 R2, please comment and vote on these Connect items:</p>
<p>&nbsp; &nbsp;&nbsp;<a target="_blank" href="http://connect.microsoft.com/SQLServer/feedback/details/814658/release-final-service-packs-for-sql-server-2008-and-2008-r2">Connect #814658 : Release Final Service Packs for SQL Server 2008 and 2008 R2</a>
</p>
<p>&nbsp; &nbsp;&nbsp;<a target="_blank" href="http://connect.microsoft.com/SQLServer/feedback/details/814600/release-service-pack-3-for-sql-server-2008-r2">Connect #814600 : Release Service Pack 3 for SQL Server 2008 R2</a></p>
<p><span><i>&nbsp;</i>&nbsp;</span></p>December 2013 Cumulative Update for SQL Server 2008 R2 SP2http://sqlblog.com/blogs/aaron_bertrand/archive/2013/12/16/december-2013-cumulative-update-for-sql-server-2008-r2-sp2.aspxMon, 16 Dec 2013 19:36:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:52158AaronBertrandMicrosoft has released Cumulative Update #10 for SQL Server 2008 R2 Service Pack 2.
<ul>
<li><span>KB Article: <a target="_blank" mce_href="http://support.microsoft.com/kb/2908087" href="http://support.microsoft.com/kb/2908087">KB #2908087</a></span></li>
<li><span>15 fixes listed at time of publication</span></li>
<li><span>Build number is 10.50.4297</span></li>
<li><span>Relevant for @@VERSION 10.50.4000 through 10.50.4296</span></li>
</ul>
<p><span><br><i>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 &gt;= 4000. If xxxx &lt; 4000, you need to start thinking about getting off the RTM or SP1 branch. Note that no more cumulative updates will be released for SP1, since support ended on October 8, 2013.<br>&nbsp;</i>&nbsp;</span></p>October 2013 Cumulative Update for SQL Server 2008 R2http://sqlblog.com/blogs/aaron_bertrand/archive/2013/11/12/october-2013-cumulative-update-for-sql-server-2008-r2.aspxTue, 12 Nov 2013 17:49:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:51709AaronBertrandMicrosoft has released Cumulative Update #9 for SQL Server 2008 R2 Service Pack 2.
<ul>
<li><span>KB Article: <a target="_blank" mce_href="http://support.microsoft.com/kb/2887606" href="http://support.microsoft.com/kb/2887606">KB #2887606</a></span></li>
<li><span>17 fixes listed at time of publication</span></li>
<li><span>Build number is 10.50.4295</span></li>
<li><span>Relevant for @@VERSION 10.50.4000 through 10.50.4294</span></li>
</ul>
<p><span><br><i>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 &gt;= 4000. If xxxx &lt; 4000, you need to start thinking about getting off the RTM or SP1 branch. Note that no more cumulative updates will be released for SP1, since support ended on October 8, 2013.<br>&nbsp;</i>&nbsp;</span></p>August 2013 Cumulative Updates for SQL Server 2008 R2http://sqlblog.com/blogs/aaron_bertrand/archive/2013/08/23/august-2013-cumulative-updates-for-sql-server-2008-r2.aspxFri, 23 Aug 2013 12:15:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:50427AaronBertrand<p>UPDATE 2013-08-23: 2008 R2 SP2 CU #8 is now available; details below.</p>
<p>UPDATE 2013-08-14: I had originally posted about SP1 CU #14, and was sure SP2 CU #8 was coming in shortly behind it, but it turns out that CU #14 has been pulled from general availability and has been converted to an on-demand hotfix update. Some people suggested this indicates some kind of quality or regression issue with the cumulative update itself, but if that were the case, it would have been pulled entirely instead of just getting a new label. This has to do with the fact that <a target="_blank" href="http://support.microsoft.com/lifecycle/search/?sort=PN&amp;alpha=SQL">SP1 support ends on October 8th</a>; I don't believe CU #14 will ever formally come to be. And just as well - you should be on the SP2 branch anyway.<br><br></p>
<p>Previous post, for posterity:&nbsp;</p>
<p>Microsoft has released a cumulative update for SQL Server 2008 R2 SP1 (and I am leaving a placeholder for the forthcoming update for SP2).
</p>
<p>
<b>SQL Server 2008 R2 Service Pack 1 Cumulative Update # 14</b>
</p>
<ul>
<li><span>KB Article: </span><a mce_href="http://support.microsoft.com/kb/2868244" target="_blank" href="http://support.microsoft.com/kb/2868244">KB #2868244</a></li>
<li><span>3 fixes listed at time of publication</span></li>
<li><span>Build number is 10.50.2881</span></li>
<li><span>Relevant for @@VERSION 10.50.2500 through 10.50.2880</span></li>
</ul>
<b><br>SQL Server 2008 R2 Service Pack 2 Cumulative Update # 8</b>
<ul>
<li><span>KB Article: <a target="_blank" href="http://support.microsoft.com/kb/2871401">KB #2871401</a></span></li>
<li><span>13 fixes listed at time of publication</span></li>
<li><span>Build number is 10.50.4290</span></li>
<li><span>Relevant for @@VERSION 10.50.4000 through 10.50.4289</span></li>
</ul>
<p><span><br><i>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 &gt;= 2500. If xxxx &lt; 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, and the fact that support for SP1 ends on October 8, 2013, you might consider abandoning SP1, too, if possible...<br>&nbsp;</i>&nbsp;</span></p>June 2013 Cumulative Updates for SQL Server 2008 R2http://sqlblog.com/blogs/aaron_bertrand/archive/2013/06/17/june-2013-cumulative-updates-for-sql-server-2008-r2.aspxMon, 17 Jun 2013 19:31:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:49736AaronBertrand
<p>Well, surely at least partly in response to <a target="_blank" href="http://www.sqlperformance.com/2013/06/system-configuration/2008-r2-hotfix-gaffe">the CU6 mess I reported earlier today</a>, and partly because they were due, Microsoft has released new cumulative updates that contain - among other things - updated code that avoids the symptom introduced with earlier updates (though this regression fix doesn't seem to appear in the KB articles - unless by "corruption" they meant ridiculous size increase).
</p>
<p>
<b>SQL Server 2008 R2 Service Pack 1 Cumulative Update # 13</b>
</p>
<ul>
<li><span>KB Article: </span><a mce_href="http://support.microsoft.com/kb/2855792" target="_blank" href="http://support.microsoft.com/kb/2855792">KB #2855792</a></li>
<li><span>5 fixes listed at time of publication</span></li>
<li><span>Build number is 10.50.2876</span></li>
<li><span>Relevant for @@VERSION 10.50.2500 through 10.50.2875</span></li>
</ul>
<b><br>SQL Server 2008 R2 Service Pack 2 Cumulative Update # 7</b>
<ul>
<li><span>KB Article: <a mce_href="http://support.microsoft.com/kb/2844090" target="_blank" href="http://support.microsoft.com/kb/2844090">KB #2844090</a></span></li>
<li><span>11 fixes listed at time of publication</span></li>
<li><span>Build number is 10.50.4286</span></li>
<li><span>Relevant for @@VERSION 10.50.4000 through 10.50.4285</span></li>
</ul>
(Also see <a target="_blank" href="http://support.microsoft.com/kb/2792921">KB #2792921</a> for information on new features in the SP2 CU7 release.)
<p><span><br><i>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 &gt;= 2500. If xxxx &lt; 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...<br>&nbsp;</i>&nbsp;</span></p>Attention users running SQL Server 2008 &amp; 2008 R2!http://sqlblog.com/blogs/aaron_bertrand/archive/2013/06/17/attention-users-running-sql-server-2008-r2.aspxMon, 17 Jun 2013 17:23:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:49724AaronBertrandIn April and May, Microsoft released cumulative updates for SQL Server 2008 and 2008 R2 (I blogged about them <a target="_blank" mce_href="http://sqlblog.com/blogs/aaron_bertrand/archive/2013/04/15/april-2013-cumulative-updates-for-sql-server-2008-r2.aspx" href="http://sqlblog.com/blogs/aaron_bertrand/archive/2013/04/15/april-2013-cumulative-updates-for-sql-server-2008-r2.aspx">here</a> and <a target="_blank" href="http://sqlblog.com/blogs/aaron_bertrand/archive/2013/05/21/may-2013-cumulative-update-for-sql-server-2008-sp3.aspx">here</a>).&nbsp;They are:
<ul>
<li>CU #11 for 2008 SP3 (10.00.5840) (<a target="_blank" href="http://support.microsoft.com/kb/2834048">KB #2834048</a>)</li>
<li>CU #12 for 2008 R2 SP1 (10.50.2874) (<a target="_blank" mce_href="http://support.microsoft.com/kb/2828727" href="http://support.microsoft.com/kb/2828727">KB #2828727</a>)</li>
<li>CU #6 for 2008 R2 SP2 (10.50.4279) (<a target="_blank" mce_href="http://support.microsoft.com/kb/2830140" href="http://support.microsoft.com/kb/2830140">KB #2830140</a>)</li>
</ul>
<p>Sometime after that, looks like the next day, both downloads were pulled, allegedly due to an index corruption issue (if you believe <a target="_blank" mce_href="http://blogs.msdn.com/b/sqlreleaseservices/archive/2013/04/15/cumulative-update-6-for-sql-server-2008-r2-sp2.aspx" href="http://blogs.msdn.com/b/sqlreleaseservices/archive/2013/04/15/cumulative-update-6-for-sql-server-2008-r2-sp2.aspx">the commentary on the Release Services blog post for CU #6</a>) or due to an issue with w3wp.exe (if you believe <a target="_blank" mce_href="http://support.microsoft.com/kb/2830140" href="http://support.microsoft.com/kb/2830140">the label on the hotfix posted directly to the CU #6 article itself</a>). Or perhaps both. At the very least you may see a regression involving index corruption when you rebuild a clustered index online and the plan involves a non-clustered index. I don't have a repro handy.</p>
<p>On June 13th, both articles were updated with new versions of the cumulative updates that no longer exhibit this symptom (<a target="_blank" mce_href="http://sqlblog.com/blogs/aaron_bertrand/archive/2009/08/06/whither-art-thou-oh-microsoft-support.aspx" href="http://sqlblog.com/blogs/aaron_bertrand/archive/2009/08/06/whither-art-thou-oh-microsoft-support.aspx">sound familiar?</a>). So if you download today, you'll actually get:
</p>
<ul>
<li>CU #11 for 2008 SP3 (10.00.<b>5841</b>) (<a target="_blank" href="http://support.microsoft.com/kb/2834048">KB #2834048</a>)</li>
<li>CU #12 for 2008 R2 SP1 (10.50.<b>2875</b>) (<a target="_blank" mce_href="http://support.microsoft.com/kb/2828727" href="http://support.microsoft.com/kb/2828727">KB #2828727</a>)</li>
<li>CU #6 for 2008 R2 SP2 (10.50.<b>4285</b>) (<a target="_blank" mce_href="http://support.microsoft.com/kb/2830140" href="http://support.microsoft.com/kb/2830140">KB #2830140</a>)</li>
</ul>
<p>Please check @@VERSION. If it reports 10.00.5840, 10.50.2874 or 10.50.4279, please go re-download and re-apply the relevant cumulative update for your branch. If you're on 2008 R2, please see <a target="_blank" href="http://sqlblog.com/blogs/aaron_bertrand/archive/2013/06/17/june-2013-cumulative-updates-for-sql-server-2008-r2.aspx">my post where I announce new CUs for the 2008 R2 branches</a>.</p>
<p>In cases like this, I really, really, really wish they would release a new, out-of-band cumulative update (this is a non-issue, now, for R2, but remains an issue for 2008 SP3 customers for another month or so). How many people go back and take another look at the CU article once they have downloaded, installed, and regression tested? Does everyone regression test a full set of online rebuilds that probably don't occur that often? I think many users will simply not see this update and are on the verge of experiencing the symptom - there simply isn't enough visibility when they quietly swap out the versions that the download links yield.
</p>
<p><i>[<a target="_blank" href="http://www.sqlperformance.com/2013/06/system-configuration/2008-r2-hotfix-gaffe%20%E2%80%8EEdit">Cross-posted on sqlperformance.com</a>]</i></p>