September 3, 2005 at 5:30 am
September 4, 2005 at 5:16 pm
Many ways to achieve this, try each and pick one that suits your need best. Also, be aware that depending on how you've designed your package you may need to edit it on the new server to change servernames, filenames, etc...
1) Edit the package in Enterprise Manager and choose Save As...
2) Transfer the rows from sysdtspackages as explained here (http://www.sqldts.com/default.aspx?204)
3) Use a tool like DTSBackup2000 (http://www.sqldts.com/default.aspx?242)
--------------------
Colt 45 - the original point and click interface
September 7, 2005 at 10:53 am
Vishal,
A very simple way, as Phill mentioned, is to 'Save As' and select structured storage file.
On the 2nd server, right-click DTS and select 'Open Package' and select the saved file. Make the any necessary changes and you SHOULD be good to go.
March 1, 2006 at 2:34 am
In my case, I developed a DTS system contains 40 DTS packages, If I use the way that you said above it will take me a lot of time and effort.
I write a simple program in VB to transfer DTS from one database to another, it works well. But when I save DTS to storage files and after that, I import DTS in to SQL Server and all DTS's layout has changed.
Any one here know which way to import DTS and their layout are not changed?
Thank you in advance.
March 1, 2006 at 2:34 am
In my case, I developed a DTS system contains 40 DTS packages, If I use the way that you said above it will take me a lot of time and effort.
I write a simple program in VB to transfer DTS from one database to another, it works well. But when I save DTS to storage files and after that, I import DTS in to SQL Server and all DTS's layout has changed.
Any one here know which way to import DTS and their layout are not changed?
Thank you in advance.
March 1, 2006 at 3:09 am
If you're saving the packages outside of SQL Server, or modifying them programmatically, then you will lose the layout and all text annotations. This is because these items are not part of the DTS object model.
If you're transferring packages between SQL Servers and have network connectivity, then checkout the DTSBackup2000 tool I mentioned in my earlier post. The tool has an option to transfer the packages and keep the layout and annotations intact.
--------------------
Colt 45 - the original point and click interface
March 1, 2006 at 12:44 pm
Vishal,
Send me a personal message with your email address than can accept an attachment. I have written a utility that will compare as well as transfer dts packages between two different servers. It avoids the need to manage any type of storage or backup files. I believe this is exactly what you are looking for. I wrote this utility to keep a dev and production environment in sync, containing over 80 packages. I would be happy to send it to you if you think it would help you solve your problem.
-Mike Gercevich
March 1, 2006 at 1:02 pm
Hi,
Thankz mike for you reply.... Please send me utility.... It will really help me....
Please send me at vishu_prajapati@yahoo.co.in
Thanking
August 24, 2007 at 2:36 am
Many Thanks for "philcart" for location of DTSBackup2000. It's exactly the tools I need. Save & restore basically three DTS is easy and fast, but when you have about fourty to do, it will be boring...
So, I'm happy :o)
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply