Hello imani_technology_spam (AT) yahoo (DOT) com,
Speed is hugely different in 2005 compared to 2000.
Your approach will be very different as well. In 2000 you could think of
DTS as ELT and in 2005 it is more ETL. There is no need to land the data
as much as previously.
DTS jobs or packages?
Packages there is a migration wizard, personally I will probably leave my
2K packages AS IS and then redo them from scratch gradually. i can use an
Execute 2000 package task to fire the old packages.
I would still use SPs in the right circumstances. You can just call them
in an ExecuteSQL task.
Allan
Quote:
I would like to compare speed. I would also like to compare
approaches. For example, is ther a way to simply transfer old DTS
jobs into SSIS? If so, would that be the most prudent approach?
Here's an example: with SQL Server 2000, it was often more efficient
to use stored procedures instead of DTS if both the source and
destination databases were SQL 2000. Would that be the case with SQL
Server 2005? |