The managment of DTS packages to various servers and to structured files can be done by going to sqldts.com and downloading the DTS2000Backup program.
It does it all, and it's free, too!!
Hi Douglas,
Thanks for the reply. I agree with you in some cases but how many servers are you managing? In a single server environment I think your points are well taken and these steps are a waste of time. In a production environment you would be backing up the MSDB and should have a copy of all this information. I mentioned this in the first article.
In the case where you have a lot of servers, coordinating the backup of all the MSDBs could be time consuming. From a developer standpoint when I have packages on a bunch of development servers I found my method rather convenient. I was able to collect the latest version of packages and put them in a database. I tried saving as *.dts files but it was a lot of work to gather the 10 to 12 packages off 3 different servers.
I also looked into the SQL2000backup mentioned in the other post but I found it to be single server based but to be honest I hadn't looked at it in a while.
I know how busy most DBAs are so I would hate to waste anyone's time but hopefully the article allows one to get ideas on how to attack problems using alternate methods.
I liked the article. Not always you see an approach that fits a multi server environment.
Don't think it was a "waist" (sic) of time at all. If you can guarantee in a multi-developer situation that nobody has tinkered with at DTS package on a live server, then the approach of visual source safe and development servers is fine. But having the actual DTS packages from the live production server backed up gives an added level of comfort, in my opinion.
I am still amazed at how well this process has served me. It also makes it easy to keep a copy of all my DTS pacakges from various places without have to have copies of MSDB.
Bruce
