Well, I'm certainly glad I didn't bet that 3050 would be the last we'd hear about SP2. It's like alphabet soup, I think 3152 (found at http://support.microsoft.com/kb/933097/ - Thanks Chris!) could unofficially be called SP2c or SP2d now?
What an absolute mess.
<...previously in this post...>
Sorry, last update on SP2/SP2a/SP2b, I'm sure. But I wouldn't put money on it. What a fiasco this has turned into!
The newest full SP2 download, obtained 2007-03-05 onward, when installed, yields @@VERSION = 9.00.3042.00, just like the previous one (the updated Service Pack includes newer DLLs for maintenance plans, so it shouldn't affect @@VERSION). You can install the post-SP2 hotfix to get to 9.00.3050.00, but I'm not sure what you get for those 8 extra build increments -- waiting for official word.
If you don't know when you downloaded SP2, you can check the version of the file SQLServer2005SP2-KB921896-x86-ENU.exe (for 32-bit Windows, at least). It should be 9.0.3042.1. If the version is lower, I suggest re-downloading from http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-8f0c-63fa18f26d3a -- a much cleaner option than installing the old, broken version you have, and then applying an 18 MB hotfix.
In any case, if you haven't yet downloaded/installed SP2, you may want to hold on until all the dust settles. My guess is that there will be a Service Pack 2b before long, because of all of the problems around maintenance plans that keep getting discovered. Here is one a colleague ran into:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262122
<...previously in this post...>
If you downloaded SP2 prior to 2007-03-05, installing it will yield @@VERSION = 9.00.3042.00. If you install the hotfix, you will be up to 9.00.3050.00.
The hotfix is described in http://support.microsoft.com/kb/933508 and can be obtained at this URL:
http://www.microsoft.com/downloads/details.aspx?FamilyId=e2c358a1-ecc4-4c49-8f65-daa6b7800eec
<...previously in this post...>
Microsoft quietly posted an update to Service Pack 2. Note that the date/time and build number have changed to 2007-03-05 and 9.00.3042.01 (according to the page) respectively. So, if you have installed SP2 or are about to, you might want to grab the most up-to-date bits:
http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-8f0c-63fa18f26d3a&DisplayLang=en
This sounds a lot like the SP3/SP3a debacle we had with SQL Server 2000.
So, what is different? Sources say that they have fixed the Maintenance Plan problem they introduced with the initial release of Service Pack 2 -- you know, the one where in cleanup tasks, days were interpreted as hours, or hours were interpreted as minutes, or something like that. So if you had a maintenance plan to do a full backup every hour, and transaction log backups every minute, and a cleanup task to delete all transaction logs more than 12 hours old, then every hour at about 14 minutes after the backup, the cleanup task was breaking the log chain by deleting all log backups more than 12 minutes old (which would include log backups *after* the last full backup!). This seems like something that should have been caught in QA and regression testing, IMHO. However, given events over the past couple of days, I'm the last person to start shooting my mouth off about proper testing. :-)