Many of you are probably asking, "Where is Service Pack 1 already?" Patience, friends. It will come in due time. In the meantime, you can see if any of the fixes in CU7 for RTM are applicable to symptoms you are experiencing (there are 33 fixes in total, so look carefully):
The build number for CU #7 is 10.50.1777.
I am a passionate technologist with industry experience dating back to Classic ASP and SQL Server 6.5. I am a long-time Microsoft MVP, write at Simple Talk, SQLPerformance, and MSSQLTips, and have had the honor of speaking at more conferences than I can remember. In non-tech life, I am a husband, a father of two, a huge hockey and football fan, and my pronouns are he/him.
Yes, but did you read the policy? There can still be fixes for those who have extended support. I suspect you won't see many of these, especially beyond July 11. But don't be shocked to see more build #s out there, as there will still be occasional fixes. Mainstream support ending does not mean, "No new builds. Period."
Aaron,
I just wasn't expecting to see any reference to an SQL2005 build greater than the SP4 CU3 and SP3 CU15. As most of us know SQL2005 is now out of Mainstream Support.
Chris
Chris, an on-demand hotfix is not the same as a CU, and I doubt you will see hotfixes like this rolled into a new CU for SQL Server 2005 (never mind back-ported into one that has already been released). I'm actually really surprised this one is being offered as an on-demand hotfix, given the current support policy as defined here:
http://www.microsoft.com/sqlserver/en/us/support/support-updates.aspx
(Switch to the 2005 tab.)
But again, I have to stress, do not expect a new cumulative update for SQL Server 2005. If this issue affects you, download the hotfix, otherwise don't…
Aaron,
You published this before the Release Services Blog mentioned it. There is an interesting KB on the SQL Browser http://support.microsoft.com/kb/2526552 that is for SQL2005 as well as SQL2008R2. What makes it interesting is that it is in build 5267 of SQL2005, which comes after the last public SQL2005 SP4 build.
Are MS issuing a refresh or SP4 CU3?
Chris
Thnx for the notice!
Hey, I see that it includes a fix for the
Intellisense vs. SQL Server 2008 vs. Visual Studio 2010 bug. Not bad!