Share via

SQL Server 2005 SP2 Critical Update

  • Article

 

What is the issue?

 

When SQL Server 2005 was released, cleanup intervals were measured in days, weeks, months, or years. In response to customer feedback, SQL Server 2005 SP2 includes significant enhancements to maintenance plans. These include an enhancement that lets users specify the cleanup interval in hours.

The change in intervals caused the initial release of SQL Server 2005 SP2 to misinterpret existing cleanup task intervals in maintenance plans and Integration Services packages. This can lead to the files being cleaned up earlier than intended. The issue is described in detail here.

 

What if I have already installed SP2 on my server?

 

If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007, install a general distribution release (GDR) update for those SQL Server 2005 SP2 installations. The GDR is available at the Microsoft Download Center:

 

Critical Update for SQL Server 2005 Service Pack 2

 

After you install this GDR, you might have to restart your computer.

 

This GDR is also available through Microsoft Update, and will be applied automatically if you are using automatic updates. However, if you are using failover clustering, you must download and apply the GDR manually. Microsoft Update will not apply the GDR to failover cluster nodes.

 

What if I haven't yet installed SP2 on my server?

 

SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the current SQL Server 2005 SP2 download is updated to resolve this issue. If you have not installed the initial release of SP2, you can download the current release and install it.

Note: If you try to apply the SP2 refresh over a previous SP2 installation, no files are updated. Instead, use the general distribution release (GDR) update below.