Anyone come up with good Environment controls inside DTS to migrate a DTS
package from Dev-->Test-->Pre-Prod-->Prod?

What I want is the package to be aware of what environment it lives on - and
based on that it knows to use different DB's.

If the package lives on DEV it knows to use DEV DB's whereas if it lives on
Production - it knows to use Live Prod data.

Problem DBA faces now when we promote packages he must manually open
packages and change connections based on the environment.

I started developing code pulling information from a DB I created and looked
up what connections to use based on calling @@ServerName. It works
something like "...I live on TEST server, so I know to use SQLTest Box and
Test DB's...so dynamically adjust connections on the fly..."

But it is a struggle to get it to work right. You get different results when
developing it, different when it's scheduled - and yet different on a whole
different machine. I'm getting frustrated and am thinking there is a better
way...


--
___________________________
Joe Horton
Database Developer / Software Engineer
WISHA/Legal Services Software Development
Department of Labor and Industries
Voice (360) 902-5928 fax (360) 902-6200

Are you using 2000?
If yes then look at the Dynamic Properties Task

If not then you can still be inventive and use a DatPump task, Global
Variables and Cliconfg



--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.allisonmitchell.com - Expert SQL Server Consultancy.
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"Joe" <nwservices (AT) olynet (DOT) com> wrote