SQL Server developers and administrators are no strangers to Data Transformation Services (DTS) packages. They likely develop DTS packages to perform everything from simple database operations to data aggregation. As such, when they upgrade some or all of their servers to SQL Server 2005, they must decide what to do with all of their DTS packages.
If you find yourself in this scenario, it can get hectic. The number of DTS packages you've created is probably not trivial, and as a DBA or developer in a perpetually changing environment that demands more with less, every minute counts. You must move quickly but remain thorough. With DTS literally everywhere, how do you assess the scope of a database change on your DTS packages? Short of opening and examining each package, what are the other options? Fortunately, there is a solution: the DTS class library.
The article continues at