- 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.
Users of SQL Server 2000 legacy maintenance plans and 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.
Note This problem only affects the main SQL Server 2005 SP2 packages. These packages use the following naming convention:
The following table lists the file version of the affected version of the SQL Server 2005 SP2 package together with the refreshed version of this package.
|Package type||File version|
|Affected self-extracting executable file||9.0.3042.0|
|Refreshed self-extracting executable file||9.0.3042.1|
The change in intervals caused the initial release version of SQL Server 2005 SP2 to interpret cleanup task intervals differently than the original settings. This behavior can cause cleanup tasks to delete information earlier than intended.
The change in intervals also caused different interpretations of cleanup task intervals if you mixed versions of the tools and of the servers. Although the original release version of SQL Server 2005 (the RTM version), SQL Server 2005 Service Pack 1 (SP1), and the SQL Server 2005 SP2 refresh are compatible, mixing these versions with the initial release version of SQL Server 2005 SP2 could lead to task intervals being interpreted incorrectly in new and modified tasks:
- If you create or modify plans or packages by using the original release version of SQL Server 2005, SQL Server 2005 SP1, or the refreshed SQL Server 2005 SP2 tools, and then you run them on the initial release version of SQL Server 2005 SP2, most cleanup task intervals are shorter than intended. This behavior could delete information earlier than intended.
- If you create or modify plans or packages by using the initial release version of SQL Server 2005 SP2 tools and then run them on the original release version of SQL Server 2005, SQL Server 2005 SP1, or the SQL Server 2005 SP2 refresh, cleanup task intervals are longer than intended. This behavior could retain information longer than intended.
- If you create or modify plans or packages by using the initial release version of SQL Server 2005 SP2 tools, select the year interval, and then open the task in the original release version of SQL Server 2005 or in SQL Server 2005 SP1, the following error can occur:InvalidArgument=Value of '4' is not valid for 'SelectedIndex'.If you ignore the message and save the package, the original release version of SQL Server 2005 and SQL Server 2005 SP1 misinterpret the cleanup interval as days, and information is deleted earlier than intended.
Parameter name: SelectedIndex (System.Windows.Forms)
If you have not installed SQL Server 2005 SP2The original release version of SQL Server 2005 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 version 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.
If you downloaded SQL Server 2005 SP2 before March 05, 2007If you downloaded SQL Server 2005 SP2 before March 05, 2007, apply the general distribution release (GDR) update for those SQL Server 2005 SP2 installations. The GDR update is available at the Microsoft Download Center:
After you apply this GDR update, you might have to restart the computer.
The GDR update corrects the interpretation of cleanup tasks that were created by using the original release version of SQL Server 2005 and by using SQL Server 2005 SP1. If you created or edited maintenance plans or Integration Services packages by using the initial release version of SQL Server 2005 SP2, you must verify and update the cleanup task intervals after you apply the GDR update. If you do not do this, cleanup tasks will retain data longer than intended.
To verify and update cleanup task intervals, follow these steps:
- Open the maintenance plan or the Integration Services package.
- Open each cleanup task.
- Adjust the cleanup interval to the correct value.
- Save the plan or the package.
Files that are updated by the GDR update and by the SP2 refresh
|Updated file||Initial SP2 release version||SP2 refresh version||Post-GDR update version||Location|
|Microsoft.SqlServer.MaintenancePlanTasks.dll||9.00.3042.00||9.00.3043.00||9.00.3050.00||%ProgramFiles%\Microsoft SQL Server\90\DTS\Tasks and the global assembly cache (GAC)|
The GDR update detects file versions and updates the files as necessary. However, if you need to verify file versions, you can use Microsoft Windows Explorer or the Filever command-line utility:
- To check the file version on individual computers, open Windows Explorer, right-click the file, select Properties, and then click the Version tab.
- To help with checking file versions on many computers, the Filever command-line utility is available. For more information about the Filever command-line utility, click the following article number to view the article in the Microsoft Knowledge Base:913111 How to use the Filever.exe tool to obtain specific information about a file in Windows
Files that are updated by all SQL Server 2005 hotfixes and GDR updatesSome files are updated by every SQL Server 2005 hotfix and GDR update, even if no changes were made in the source code. For example, if Sqlservr.exe is updated, SELECT @@version shows an updated product version.
The following table lists the files that are updated regardless of code changes.
|Updated file||Initial SP2 release version||SP2 refresh version||Post-GDR update version|
Article ID: 933508 - Last Review: Jun 21, 2014 - Revision: 1