Abt DTS mass migration

Two servers with different name and IP
We have to transfer around 500 DTS packages to the new server. But can not restore the MSDB to new server, and also can not DTS all the packages to new server in one step. Any tips for DTS mass migration? Or we have to save as one by one manually? Thanks in advanced.Hi there,

I don't know if this helps you further, but I use the "DTSBackup 2000" tool for transferring DTS packages from one server to another. You can find out more about this tool at http://www.sqldts.com/?242

Greetings,
Carsten|||Thank u very much. Let me try...

Originally posted by CarstenK
Hi there,

I don't know if this helps you further, but I use the "DTSBackup 2000" tool for transferring DTS packages from one server to another. You can find out more about this tool at http://www.sqldts.com/?242

Greetings,
Carsten

about connections and Login

Hey guys,

I have created dtsx packages and i have one master package which would run couple of child packages.

1. I have all on my local machine.I want others who r working with me access these.So what do i need to do?for them to access...

2.what would be the best way in executing these packages.

the way it is set now is i had 3 connections set for each package.

a.Source connection

b.Destination Connection.

c.One more connection(which is used with in the process of execution)

Can i set connections in common for all the packages in one location.

3.i also want to set some logging settings to my master package too.and i want this package to run everyday automatically at a particular time how can this be done.

How can i do that.

please let me know.

sureshv wrote:

1. I have all on my local machine.I want others who r working with me access these.So what do i need to do?for them to access...

What you mean, to edit them? just use VSS or place them in a shared location. To execute them, place them in a shared location and then set up a Job (SQl Agent) to run them.

sureshv wrote:

2.what would be the best way in executing these packages.

Via SQL Agent job would be my preferred method

sureshv wrote:

Can i set connections in common for all the packages in one location.

No, but you can use package configuration instead.

sureshv wrote:

3.i also want to set some logging settings to my master package too.and i want this package to run everyday automatically at a particular time how can this be done.

To schedule them, again, use a SQL Agent Job. For logging just enable package logging.