We have some old Microsoft SQL Server 2000 DTS package files ( that have dts extension ).
I need to import the old DTS package files to a Microsoft SQL Server 2008 Management Studio.
Download Now WinThruster 2018 - Scan your PC for SQLServer2005_BC.msi registry errors. Compatible with Windows 10, 8, 7, Vista and Windows XP. //Microsoft SQL Server 2005 Enterprise Edition/Tools/Setup/SQLServer2005_BC.msi //Microsoft SQL Server 2005 Enterprise Edition/Servers/Setup/SQLServer2005_BC.msi. Look for the SQL2005_BC.msi file in the SQL 2008 media x64 Setup x64 folder and run that. 2008 R2, 2008 and 2005. 14 Mar 2017: now over 40,000 downloads.Disclaimer: All information provided. Downloads; sqlncli_x64.msi cannot be found while installing SQL Server 2005 64bit on Windows Server 2008 R2. February 27, 2011 All, General, KnowledgeBase, SQL Server, SQL Server 2005, Troubleshooting, Windows, Windows 2008 R2.
I read the following guide, but I fail to find any Legacy folder under the Management folder within the Microsoft SQL Server 2008 Management Studio Object Explorer View:
I need to import the Microsoft SQL Server 2000 DTS package files into the Microsoft SQL Server 2008 Management Studio.
Please suggest how I can resolve the issue
Follow Up on my experience in importing the DTS packages to my Microsoft SQL Server 2008 DTS package files:
Managing DTS packages in SQL Server Management Studio requires the SQL Server 2000 Data Transformation Services (DTS) runtime. To install the DTS runtime, on your SQL Server 2008 R2 installation media, locate and run the Windows Installer package for SQL Server 2005 Backward Compatibility (SQLServer2005_BC*.msi). You can also download the DTS runtime from the SQL Server Feature Pack page on the Microsoft Download Center. (Microsoft.SqlServer.DtsObjectExplorerUI)
Program Location:
at Microsoft.SqlServer.Dts.ObjectExplorerUI.PackageUtils.LoadPkgInfoFromStorageFile(String sUNCPath) at Microsoft.SqlServer.Dts.ObjectExplorerUI.LegacyActionBase.ShowPkgBrowser(String& sPackageName, String& sPackageID, String& sPackageVersionID, StorageLocation location, String sPackagePathName)
Support for SQL Server 2000 DTS in SQL Server 2008 R2SQL Server 2008 R2Other Versions4 out of 6 rated this helpful - Rate this topic
Although SQL Server 2000 Data Transformation Services (DTS) is deprecated, SQL Server 2008 provides optional 32-bit management, run-time, and design-time support for packages that were created by using the DTS tools and object model. (For more information about the deprecation of DTS, see Data Transformation Services (DTS).)NoteNote
For SQL Server 2008 R2, there have been no changes to the content that is listed in this topic.Important noteImportant
The features described in this topic, including run-time support for DTS packages, require the manual installation of additional, optional components that are not available during setup. For more information, see the sections, 'Installing run-time support for DTS packages ' and 'Installing design-time support for DTS packages,' later in this topic.
Be aware that not all DTS functionality is supported in all circumstances. The following sections describe exactly what DTS functionality is supported in SQL Server 2008.Limited SQL Server 2000 DTS Functionality on 64-bit Operating Systems
SQL Server 2008 does not include support for DTS in the following circumstances:
Supported SQL Server 2000 DTS Functionality
SQL Server 2008 includes support for the following DTS features:
Important noteImportant
The Execute DTS 2000 Package task, the ActiveX Script task, and the DTS Package Migration Wizard are installed when you select Integration Services for installation. However, these components are not fully functional without the manual installation of additional, optional components that are not available during Setup. For more information, see the section, 'Installing run-time support for DTS packages,' later in this topic.
The remainder of this topic discusses in more detail the DTS functionality that SQL Server 2008 supports. Use the following links to quickly connect you to this content:
General information
Designing and running DTS packages
Migrating DTS packages
Limited support
General Compatibility between SQL Server 2000 DTS and Integration Services
DTS and Integration Services are completely different products. Integration Services is not a version upgrade from DTS. Therefore, there are no software conflicts between DTS and Integration Services. You can do the following procedures:
When you upgrade an existing instance of SQL Server to SQL Server 2008, the system tables (for example, sysdtspackages) that DTS uses in the msdb database remain intact. DTS packages are not automatically migrated. For information about how to migrate packages, see the section, Migrating DTS packages.
Arrow icon used with Back to Top linkBack to the top of this sectionManaging SQL Server 2000 DTS Packages
After you install the optional run-time support for DTS as described in the section, 'Installing run-time support for DTS packages,' you can manage DTS packages from SQL Server Management Studio. These DTS packages can be stored in an instance of SQL Server 2000, or imported to and stored in an instance that is running SQL Server 2005 or a later version.Important noteImportant
For important information about how to secure DTS packages, see Securing DTS Packages Stored in SQL Server.
To view DTS packages in Management Studio, first connect to an instance of SQL Server. (Do not connect to an instance of Integration Services.) Then, in the Object Browser under the ManagementLegacyData Transformation Services node, you will be able to perform the following tasks:
The Integration Services database-level roles grant rights on the Integration Services system tables in the msdb database, but not on the DTS system tables, such as sysdtspackages in the msdb database. You have to grant users rights on the DTS system tables before they can perform certain management tasks, such as importing a DTS package in Management Studio. For information about the Integration Services database-level roles, see Using Integration Services Roles.
Arrow icon used with Back to Top linkBack to the top of this sectionInstalling Run-time Support for SQL Server 2000 DTS Packages
Although you can run DTS packages and Integration Services packages on the same computer, SQL Server 2008 does not install run-time support for DTS packages. You have to install this run-time support before you can run and manage DTS packages. For information about how to install run-time support for DTS, see How to: Install Support for Data Transformation Services Packages.
The backward compatibility files that provide run-time support for DTS packages also include run-time support for the SQL Server 2000 Analysis Services Processing task and its dependency, Decision Support Objects (DSO). However, the backward compatibility files do not include design-time support for modifying DTS packages that contain the SQL Server 2000 Analysis Services Processing task. You can modify packages that contain this task only when you have SQL Server 2000 Analysis Services installed on the same computer.
The backward compatibility files that provide run-time support for DTS packages do not include support for the SQL Server 2000 Data Mining Prediction Query task.
Arrow icon used with Back to Top linkBack to the top of this sectionRunning SQL Server 2000 DTS Packages at the Command Prompt
You can run DTS packages at the command prompt. Integration Services installs the dtsrun.exe utility when it installs DTS run-time support.
Arrow icon used with Back to Top linkBack to the top of this sectionRunning SQL Server 2000 DTS Packages from SQL Server Agent Jobs
To run DTS packages from a SQL Server Agent job, you must set the job step to Operating system (CmdExec) and use the dtsrun utility (dtsrun.exe) to run the package. You cannot set the job step to SQL Server Integration Services Package. For more information, see How to: Run a Package.
Arrow icon used with Back to Top linkBack to top of this sectionRunning SQL Server 2000 DTS Packages from Integration Services Packages
You can also run DTS packages as part of an Integration Services package. Integration Services provides the Execute DTS 2000 Package task for running DTS packages within an Integration Services package. For more information, see Execute DTS 2000 Package Task.
Arrow icon used with Back to Top linkBack to top of this sectionInstalling Design-time Support for SQL Server 2000 DTS Packages
DTS packages cannot be opened or modified directly in Business Intelligence Development Studio. In addition, neither SQL Server 2008, nor SQL Server 2005, installs the DTS package designer for modifying DTS packages. However, you can download and install the DTS package designer, and use it to modify DTS packages. For information about how to install design-time support for DTS packages, see How to: Install Support for Data Transformation Services Packages. After installing this download, you can view and modify DTS packages from Management Studio, or from the Execute DTS 2000 Package Task Editor in Business Intelligence Development Studio.
For information about how to manage certain DTS application properties that affect the DTS design environment, see Setting DTS Application Properties.
Arrow icon used with Back to Top linkBack to top of this sectionMigrating SQL Server 2000 DTS Packages
SQL Server provides the DTS Package Migration Wizard for migrating DTS packages to the Integration Services package format. When you select Integration Services for installation, Setup also installs the DTS Package Migration Wizard. You can optionally use the DTS Package Migration Wizard to upgrade DTS packages to the Integration Services format. During migration, the wizard copies the DTS packages and then re-creates them in the Integration Services format. The source packages are left intact and are not modified.NoteNote
The DTS Package Migration Wizard is available in the following editions of SQL Server: Standard, Enterprise, and Developer.
Many packages can be fully migrated to Integration Services, especially DTS packages that use tasks, connections, and other objects that have an equivalent in Integration Services. Other packages can be migrated successfully by encapsulating certain tasks or features that cannot be migrated in an Execute DTS 2000 Package task. For more information, see Migrating Data Transformation Services Packages.
Before running the DTS Package Migration Wizard, you might want to install and run Upgrade Advisor to analyze your existing packages for migration issues. For more information, see Using Upgrade Advisor to Prepare for Upgrades.NoteNote
Upgrade Advisor cannot analyze, and the DTS Package Migration Wizard cannot migrate, DTS packages that are saved in the msdb database of an instance of SQL Server 7.0. However, the Upgrade Advisor can analyze, and the DTS Package Migration Wizard can migrate, SQL Server 7.0 DTS packages that are saved as structured storage files. Also, the Upgrade Advisor can analyze, and the DTS Package Migration Wizard can migrate, SQL Server 7.0 DTS packages that are saved in the msdb database of an instance of SQL Server 7.0 that has been upgraded to SQL Server 2005 or a later version.
Arrow icon used with Back to Top linkBack to the top of this sectionMigrating Command Lines for Executing Packages
To understand how the command-line options for the SQL Server 2000 DTS dtsrun utility (dtsrun.exe) map to the options for the Integration Services dtexec utility (dtexec.exe), see Mapping dtsrun Options to dtexec Options.
Arrow icon used with Back to Top linkBack to the top of this sectionSupport for ODBC Data Sources
Sqlserver2005_bc Msi Download Free
To load or save data to an ODBC data source, you can use an ADO.NET source or destination and select the .NET Framework Data Provider for ODBC. It is also possible to use the Script component to create an ad hoc ODBC source or destination for use in a single package. For more information, see Creating an ODBC Destination with the Script Component.
Arrow icon used with Back to Top linkBack to the top of this sectionSupport for Meta Data Services (Repository) Packages
SQL Server 2000 Meta Data Services, typically known as the Repository, is a deprecated component. SQL Server 2005 and later versions do not install or use the Repository.
The DTS designer and the dtsrun utility continue to support DTS packages that were saved to the Repository.
Integration Services supports the Repository only in the Upgrade Advisor and the DTS Package Migration Wizard, and only if the Repository redistributable files are installed on the local computer. (These files are normally present when the computer has either SQL Server 2000 or the SQL Server 2000 tools installed.) When the Repository redistributable files are present, the Upgrade Advisor can scan, and the DTS Package Migration Wizard can migrate, DTS packages that were saved to the Repository. When the Repository redistributable files are not present, the Upgrade Advisor and the DTS Package Migration Wizard can only be used on DTS packages that were saved to SQL Server or to structured storage files.
The Integration Services Execute DTS 2000 Package task cannot run a DTS package that was saved to the Repository. However, the SQL Server 2000 DTS runtime can run such a package. Thus, to have an Integration Services package run a DTS package that is stored in the Repository, follow these steps:
Arrow icon used with Back to Top linkBack to the top of this sectionSupport for SQL Server 2000 DTS Packages in SQL Server Express
SQL Server Express does not include Integration Services nor does it support DTS packages. However, you can work with DTS packages on a server that is running SQL Server Express by using one of the following methods:
Arrow icon used with Back to Top linkBack to the top of this section
Integration Services icon (small) Stay Up to Date with Integration Services
See AlsoConceptsKnown DTS Package Migration IssuesMapping dtsrun Options to dtexec OptionsSetting DTS Application Properties64 bit Considerations for Integration Services
1 Answer
DTS packages can still run as before when you have the SQL Server 2008 database engine installed. To accomplish this, you must have the Microsoft SQL Server Backward Compatibility feature installed from the SQL Server installation media or the Feature Pack Web page. This installs the DTS runtime for SQL Server 2008, which works on 32-bit platforms only.
After you install this feature the Legacy folder will appear under Management node
For 64bit runtime follow this link (Feature Pack for Microsoft SQL Server 2005 - December 2008) and from the list of available downloads select SQLServer2005_BC_x64.msi