SQL Server DTSDiscussion specific to Data Transformation Service with SQL Server. General SQL Server discussions should use the general SQL Server forum. Readers of the book Professional SQL Server 2000 DTS with questions specific to that book should post in that book forum.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the SQL Server DTS section of the Wrox p2p Programmer to Programmer discussion community. This is a community of more than 40,000 computer programmers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining our free Wrox p2p community you can post your own programming questions and respond to other programmers’ questions. Registered users also don't have to see the ads that are displayed to guests. Registration is fast, simple and absolutely free so please, join today!
Join today and post to win prizes! Post more to increase your chances of being Wrox’s top poster of the month.
I have all the packages saved in the SQL Server, now they planned to scrape the existing system and would need to move it to the new server. What is the best recommended way to move all the packages from one server to another.
Currently, I'm exporting the packages to the filesystem as .DTS file and importing it to the new server, one by one and change the conn string info. in the target server manually.
As you know, its a time consuming process of copying the package one by one. Is there any other way to copy it to the new server? Will backup and restore of MSDB help in these aspects? Also, way to change conn string of db only by an automated process.
The other way, what i felt was open the package in the existing system and use "Save as" option pointing to the new server...
DTS copy
Linear Mode
