… your options include
1. Saving the DTS packages to the new server and executing them directly.
2. Running DTS Migration Wizard and letting it convert the packages to SSIS packages for control flow invoking DTS components for the data flow.
3. Rewriting DTS packages completely in SSIS.
Neither option guarantees a performance gain. In fact, moving data directly from a source to a destination table without much transformation logic you will likely see similar performance for all the options. So unless you are taking advantage of new features in SSIS, you are better off selecting the option that fits best into your operating procedures.
If you continue using DTS packages on the new server, you will certainly need Microsoft SQL Server 2000 DTS Designer Components. That applies to options 1 and 2. With option 2, the Migration Wizard generates SSIS control flow, but creates an embedded DTS package for every Data Pump, instead of converting it to a Data Flow Task. Option 3 will likely require the most amount of work, and that's where the fun begins!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment