Its probably a little late for this kind of question but, I'm converting several DTS packages over to SSIS and in the conversion I have the ability to run tasks as 'Execute DTS 2000 Package'. My question is, should I use that or do a full re-write of the flows to use the SSIS tasks?
So far I've been removing anything pertaining to SQL 2000 and adding the SSIS tasks. Its becoming very time consuming this way due to some of the DTS packages have a lot of tasks/flows. Is it the best way to do this or should I just use the DTS migration Wizard and then leave the .dtsx files alone once they're created from the wizard?
The Migration Wizard and the Execute DTS 2000 task should be seen as a short-term fix. The correct solution is to re-write your packages in SSIS. The Migration Wizard is not able to make architectural decisions to take advantage of the new capabilities in SSIS. Also, the DTS run-time probably has a limited lifespan. I have not heard anything about DTS support in 2008, but I wouldn't expect it based on what was said when 2005 was released.
|||
thanks, I was thinking the samething. So far I've rewrote almost 40 of them but I was curious on the DTS 2000 task though.
I have 40 down and 110 more to do to rewrite.
No comments:
Post a Comment