I was just wondering of a good method of releasing a DTS from a test server
to Production.

Are there any tried & tested methodologies for doing this?

Bearing in mind that the connection properties will need to be amended in
some cases, and any File related issues (e.g. file existing on users machine
and not on LIVE server) will need to be monitored..

Many thanks

It's a good practice to use a Dynamic Properties task to initialize things
like connections and file paths. You can even use an INI file to contain
this info. Simply change the values in the INI file when you go to prod.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com

"Ben Rum" <bundyrum75 (AT) yahoo (DOT) com> wrote

Thanks for the info. I use UDL files for all connections, which I find to be
handy for updating properties easily.

I was more getting at how to move the changes (be it a NEW dts or UPDATE to
an existing one) from the dev server to prod. Would I look at saving the
DTS as file, and importing into the live server. Or physically re-creating
the DTS as per the development server...?


"Tom Moreau" <tom (AT) dont (DOT) spam.me.cips.ca> wrote

You can save it as a file and import it. Or you can do a
Save as and when saving it to SQL Server, change the server
value to the production server. It will save the package on
that server.

-Sue

On Mon, 17 Oct 2005 15:16:12 +0100, "Ben Rum"
<bundyrum75 (AT) yahoo (DOT) com> wrote: