Hint for SQL Server 2005 Backward-Compatibility

I recently installed SQL Server 2005 Developer Edition on my laptop. I upgraded the default instance of SQL Server 2000, but didn't upgrade four other instances of SQL Server 2000 on my laptop. Now, I can't edit SQL Server 2000-based DTS packages in any of the instances, and yes, I have installed the SQL Server 2000 DTS Designer Components that are part of the Feature Pack for Microsoft SQL Server 2005.

Let's start with some background about the Feature Pack for Microsoft SQL Server 2005. This feature pack is a collection of standalone installation packages that provide additional value for SQL Server 2005.The collection includes the latest versions of the following:

One of the standalone installation packages included in this feature pack is the SQL Server 2000 DTS Designer Components, which are required to edit SQL Server 2000 DTS packages from a SQL Server 2005 environment. However, solving the reader's problem requires performing one additional step that's documented in the Microsoft article "SQL Server 2005 Integration Services Backward Compatibility" at http://msdn2.microsoft.com/en-us/ library/ms143706.aspx.(Note that this article is in the December 2005 refresh of SQL Server 2005 Books Online—BOL.) This article indicates that "although support for SQL Server 2000 DTS is installed automatically when you select Integration Services for installation, some of the registry and environment settings required by DTS are removed if you upgrade the last instance of SQL Server 2000 on the computer to SQL Server 2005 during or after setup." To restore the registry and environment settings required by DTS, access the Control Panel, select the Add or Remove Programs icon, and select the Microsoft SQL Server 2005 Backward compatibility option. Click Change, and on the Program Maintenance page of the wizard, select Repair. That should do the trick if you're having a similar problem.