More news on Service Pack 2 and Maintenance Plans

So I have official word (and permission to broadcast) that there is one minor bug left in maintenance plans, in the wake of last week's difficulties in properly addressing SP2 and the fixes that followed.  We should expect a GDR early next week and a QFE rollup within a week of that.  No, I don't have build numbers yet, and no, I don't know exact dates.  But if you're using maintenance plans and have held off installing SP2 or the followups until now, wait until the GDR is released.  I will try to stay on top of it, and will publish something here as soon as I hear anything.

Aaron Bertrand

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 father of two, a huge hockey and football fan, and my pronouns are he/him. If I've helped you out, consider thanking me with a coffee. :-)

3 Responses

  1. AaronBertrand says:

    Thanks, there are two new builds, 3054 and 3159, which one you are supposed to apply depends on what you have now.  Really, really messy.  I posted details on both in a new entry before I saw these comments.

  2. Chris Wood says:

    I notice this fix includes an update to Microsoft.sqlserver.maintenanceplantasks.dll
    Maybe your fix is getting closer to be published.

  3. AaronBertrand says:

    A comment I posted on K. Brian Kelley's blog (you'd have to read his entry for context, but basically he observed that was updated today):
    I think they only updated the article with more disclosure about what actually happened… I'm fairly confident the actual bits in the hotfix there (and the 3152 QFE) remain unchanged, and the final minor issue we have will be resolved within 7 days (GDR) and 14 days (QFE rollup).
    If you watched the SP2 download page on the Friday when the issue was first fixed, they quietly swapped out the executable instead of providing full disclosure (personally, I think they should have pulled the download).  I think they're owning up to that now, but I can understand they still have a hard time reaching all of the people who downloaded the service pack prior to the issue being discovered (and many of those may not have even installed the service pack yet).