<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results matching tags 'cumulative updates' and 'CU3'</title><link>http://sqlblog.com/search/SearchResults.aspx?o=DateDescending&amp;tag=cumulative+updates,CU3&amp;orTags=0</link><description>Search results matching tags 'cumulative updates' and 'CU3'</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>SQL Server 2008 Cumulative Update 3 is available</title><link>http://sqlblog.com/blogs/aaron_bertrand/archive/2009/01/20/sql-server-2008-cumulative-update-3-is-available.aspx</link><pubDate>Tue, 20 Jan 2009 22:39:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:11288</guid><dc:creator>AaronBertrand</dc:creator><description>&lt;p&gt;Cumulative Update Package 3 has been made available in &lt;a href="http://support.microsoft.com/kb/960484" title="http://support.microsoft.com/kb/960484" target="_blank"&gt;KB #960484&lt;/a&gt;.&amp;nbsp; This will bring your SQL Server 2008 instance(s) up to build 10.0.1787.0.&lt;/p&gt;&lt;p&gt;The most interesting fix for me was the one mentioned in &lt;a href="http://support.microsoft.com/kb/958760" title="http://support.microsoft.com/kb/958760" target="_blank"&gt;KB #958760&lt;/a&gt;: "FIX: You may experience issues when you try to expand the Databases node in SQL Server Management Studio, or the sp_spaceused stored procedure takes a long time to run in SQL Server 2008"... this is an issue that bit a LOT of people when SQL Server 2008 was first released.&amp;nbsp; See Connect items &lt;a href="http://connect.microsoft.com/sql/ViewFeedback.aspx?FeedbackID=354291" title="http://connect.microsoft.com/sql/ViewFeedback.aspx?FeedbackID=354291" target="_blank"&gt;#354291&lt;/a&gt;, &lt;a href="http://connect.microsoft.com/sql/ViewFeedback.aspx?FeedbackID=362646" title="http://connect.microsoft.com/sql/ViewFeedback.aspx?FeedbackID=362646" target="_blank"&gt;#362646&lt;/a&gt;, &lt;a href="http://connect.microsoft.com/sql/ViewFeedback.aspx?FeedbackID=383715" title="http://connect.microsoft.com/sql/ViewFeedback.aspx?FeedbackID=383715" target="_blank"&gt;#383715&lt;/a&gt;, &lt;a href="https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=354322" title="https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=354322" target="_blank"&gt;#354322&lt;/a&gt;, an entry by &lt;a href="http://is.gd/gE2S" title="http://is.gd/gE2S" target="_blank"&gt;Desirée Harris @ OrcsWeb&lt;/a&gt;, and my &lt;a href="http://sqlblog.com/blogs/aaron_bertrand/archive/2008/07/07/a-little-management-studio-oops.aspx" title="http://sqlblog.com/blogs/aaron_bertrand/archive/2008/07/07/a-little-management-studio-oops.aspx" target="_blank"&gt;previous blog post&lt;/a&gt; about the issue.&amp;nbsp; At the time there were dozens of other blog posts about this issue that I was simply too lazy to fetch when I was posting this entry.&lt;br&gt;&lt;/p&gt;&lt;p&gt;There are some other interesting fixes as well; I suggest checking out the KB article above to see if you are affected.&amp;nbsp; As always, please request the correct patch files for your platform, and test before deploying this patch to production!&lt;br&gt;&lt;/p&gt;</description></item></channel></rss>