I'm very new to DTS. I've been asked to help develop DTS packages
which will run on systems on the other side of the continent. The
client has sent samples of work done so far. He is using local
servers, and local on-disk text files in various tasks. I have
brought those up here, but of course they won't run. It appears to be
labor intensive to go through and fix all the server, database, and
disk file references throughout all the packages. So when I do have
something worked out here, then it would appear to require a fair
amount of error prone effort to make the package run at the
destination site. Also, if I need to ship a package back to evolve
it, then I have to undo, and re-do all of these localized references.

Can anyone with experience in this sort of thing recommend approaches
and techniques for making these packages as portable as possible?

TIA - Best Regards, - Lee Gillie

Take a look at the Dynamic Properties task. Set up such things as server
and database names, file paths, etc. in global variables and then initialize
the appropriate properties from the globals using the Dynamic Properties
Task.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
..
"Lee Gillie" <ANTISPAMIFICATION_lee (AT) odp (DOT) com> wrote

I'm very new to DTS. I've been asked to help develop DTS packages
which will run on systems on the other side of the continent. The
client has sent samples of work done so far. He is using local
servers, and local on-disk text files in various tasks. I have
brought those up here, but of course they won't run. It appears to be
labor intensive to go through and fix all the server, database, and
disk file references throughout all the packages. So when I do have
something worked out here, then it would appear to require a fair
amount of error prone effort to make the package run at the
destination site. Also, if I need to ship a package back to evolve
it, then I have to undo, and re-do all of these localized references.

Can anyone with experience in this sort of thing recommend approaches
and techniques for making these packages as portable as possible?

TIA - Best Regards, - Lee Gillie