DTS xChange - Tim Radney
"When I got started working with SSIS I struggled with how to make a few things work that was in place in DTS. DTS xChange was a very valuable tool to enable me to complete my project on time."

Tim Radney

Manager Information Technology

DTS xChange - Amerisource Bergen Canada
"The DTS xChange Profiler was critical to our project planning phase; the SQL migration team was able to plan its resources accordingly and accurately!"

Damian Glover

Systems Manager

Amerisource Bergen Canada

DTS xChange - Microsoft Corporation
"To streamline these DTS migrations during upgrade, DTS xChange by Pragmatic Works offers a fast and easy way to manage DTS to SSIS conversion."
Tom Casey

Sql Server Business Intelligence

Microsoft Corporation



Buy Now Free Trial Download Compare Editions
DTS xChange Migration Engine

DTS xChange not only converts DTS Package to equivalent SSIS but also you will have an opportunity to apply series of best practices during migration.

Feature Highlights

  • Discover DTS Packages, analyze complexity, and build a project plan
  • Convert packages easily, and apply best practices
  • Analyze errors, warnings, run time performance, and count analysis
DTS xChange Migration Engine

DTS xChange Migration Engine- Step 1
Before your migration project starts, find out quickly what you're about to jump into. DTS xChange offers a detailed profiling tool that allows you to scope out your DTS migration project. It's perfect for project managers, DBA managers, consultants or anyone interested in determining how much of an effort the migration is going to be.

Before your migration project starts, find out quickly what you're about to jump into. DTS xChange offers a detailed profiling tool that allows you to scope out your DTS migration project. It's perfect for project managers, DBA managers, consultants or anyone interested in determining how much of an effort the migration is going to be.

DTS xChange Migration Engine- Step 2
DTS xChange will first prompt you where your packages are located at. Packages can be read from a directory of .DTS package files or from a SQL Server 2000 machine. You're also asked where you wish the output of the wizard to be written. SQL Server 2005 and 2008 are both supported and packages can be automatically deployed to your SQL Server or just written to your file system.


DTS xChange will first prompt you where your packages are located at. Packages can be read from a directory of .DTS package files or from a SQL Server 2000 machine. You're also asked where you wish the output of the wizard to be written. SQL Server 2005 and 2008 are both supported and packages can be automatically deployed to your SQL Server or just written to your file system.


DTS xChange Migration Engine- Step 2b

DTS xChange Migration Engine- Step 3
Conversion of your packages can occur one by one or you could do hundreds at a time. Whichever method you choose, the next screen will ask you what rules you wish to apply to the packages as they're converted. The rule framework was built from best practices pioneered from converting thousands of packages to SSIS. For example, one of the rules you may want to enable is to turn on checkpointing in SSIS or to enable logging or transactions.

Conversion of your packages can occur one by one or you could do hundreds at a time. Whichever method you choose, the next screen will ask you what rules you wish to apply to the packages as they're converted. The rule framework was built from best practices pioneered from converting thousands of packages to SSIS. For example, one of the rules you may want to enable is to turn on checkpointing in SSIS or to enable logging or transactions.

DTS xChange Migration Engine- Step 4
After the rules are configured, the packages will begin to migrate. Migration can optionally validate each of the SSIS packages after migration. Validation will connect to the various sources and destinations that are used in package to confirm that the package will actually work once run in production. This is not the same as a full test with execution but it goes a long way to helping with that testing.

After the rules are configured, the packages will begin to migrate. Migration can optionally validate each of the SSIS packages after migration. Validation will connect to the various sources and destinations that are used in package to confirm that the package will actually work once run in production. This is not the same as a full test with execution but it goes a long way to helping with that testing.

DTS xChange Migration Engine- Step 5
After the migration, you're also presented a detailed log of what was done and anything that failed. If there were any validation warnings, you will see those in a separate tab in this screen. A sample validation warning may be that your table that the package is referring to does not exist or the database is invalid.

After the migration, you're also presented a detailed log of what was done and anything that failed. If there were any validation warnings, you will see those in a separate tab in this screen. A sample validation warning may be that your table that the package is referring to does not exist or the database is invalid.

View Our Suite of Pragmatic Works Products
Copyright 2014 by Pragmatic Works