To install the DTS runtime, run the SQL Server Installation Wizard. "Unable to load SQL Server 2000 Data Transformation Services (DTS) runtime. Even after installing the Client Tools Backward Compatibility and the SQLServer2008_DTS.msi you still may get the error below when you attempt to open a package. Best to refer to the Microsoft link for instructions as the installation procedure is not the smoothest. In order to edit and run DTS packages within SQL 2008 Microsoft SQL Server Management Studio (SSMS) you will need to install the Microsoft SQL Server 2000 DTS Designer Components.
WORKING WITH DTS IN SQL 2008 32-BIT VERSION Nothing prevents you from doing this, and we have found the performance of this new configuration to equal that of our previous setup. We simply chose to continue hosting the DTS packages on our old production 32-bit SQL Server 2000 box and simply change the Source and Destination connections to the new 64-bit SQL 2008 environment. We did not like this option as there are times when you want to run packages interactively and be able to edit them for troubleshooting purposes. Note: Remember to change the Source and Destination connections where necessary to the new 64-bit machine. One option around this limitation is to edit the DTS package locally or on a 32-bit server and then copy the package over to the 64-bit machine. So while it is possible, on a 64-bit machine, to install a 32-bit version of the dtexec utility (dtexec.exe) that allows you to run the DTS packages in 32-bit mode, the utility does not allow you to edit the packages. Like many companies, we wanted our new production servers to gain the performance increases from running the 64-bit edition of SQL 2008. WORKING WITH DTS IN SQL 2008 64-BIT VERSION
If you are planning an upgrade to SQL 2008 and are not ready to head down the SSIS path here are some ideas to accommodate your existing DTS packages. We knew pre-upgrade that the functionality of many of our DTS packages would soon become obsolete (in a few months) and so this did not warrant the time and expense of converting them to SSIS. Recently, we were faced with the not uncommon situation of upgrading our SQL 2000 production system directly to SQL 2008 (and bypassing SQL 2005).