SQL Server Performance

Critical Update for SQL Server 2005 Service Pack 2

Discussion in 'Forum Announcements' started by MohammedU, Mar 6, 2007.

  1. MohammedU New Member

    Critical Update for SQL Server 2005 Service Pack 2 (KB:93350<img src='/community/emoticons/emotion-11.gif' alt='8)' /><br /<a target="_blank" href=http://www.microsoft.com/downloads/details.aspx?FamilyId=e2c358a1-ecc4-4c49-8f65-daa6b7800eec&displaylang=en>http://www.microsoft.com/downloads/details.aspx?FamilyId=e2c358a1-ecc4-4c49-8f65-daa6b7800eec&displaylang=en</a><br /><br /><br />MohammedU.<br />Moderator<br />SQL-Server-Performance.com
  2. deepakontheweb New Member

    Microsoft SQL Server 2005 Service Pack 2 issue: "Cleanup tasks run at different intervals than intended"

    Accordning tohttp://support.microsoft.com/kb/933508 you need this hotfix

    only if all the following conditions are true:

    • You downloaded SQL Server 2005 SP2 before March 05, 2007, and installed that download package.
    • You use SQL Server 2005 maintenance plans or Integration Services packages.
    • Those plans or packages include History Cleanup tasks or Maintenance Cleanup tasks.

    Before this hotfix till SQL SP2 file version is 9.0.3042.0 and after applying it should be 9.0.3042.1

    Deepak Kumar
    MVP, MCDBA - SQL Server

    Disclaimer: This post is provided as is with no rights & warranty for accuracy, for the sake of knowledge sharing only.
  3. Roji. P. Thomas New Member

    If you think that is not enough, here is another gem.<br /><br />https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=262122<br /><br />My friend Frank calls these kind of stuff a "spoiler" [<img src='/community/emoticons/emotion-6.gif' alt=':(' />]<br /><br />Roji. P. Thomas<br />SQL Server MVP<br /<a target="_blank" href=http://toponewithties.blogspot.com>http://toponewithties.blogspot.com</a><br />
  4. MohammedU New Member

    Here is info from the KB article:

    Users who downloaded SP2 after March 05, 2007 are not affected. On this date, SQL Server 2005 SP2 was refreshed to include an update that avoids this issue.


Share This Page