• I'm afraid there's an element of naivety here. OK, a company may have "dozens or hundreds of SQL Server 2000 DTS packages", and - if they have enough budget - will eventually find time to re-write them. What about companies who sell DTS packages as part of their product suite? Not everyone is going to jump to SQL 2005 as soon as it's available and so those companies are obligated to continue support for both SQL 2000 and SQL 2005 within their customer base. This means they need increased resources to maintain parallel code streams, including the associated testing and documentation.
     
    Maybe I'm missing something here: why couldn't Microsoft have provided a "DTS container" that would operate as a fully-fledged IS task but which could host an existing SQL 2000 DTS task. In other words, providing the necessary software interfaces and abstractions to allow a DTS task to run unchanged within IS.