Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rookie_sql
Constraint Violating Yak Guru
443 Posts |
 Posted - 2010-04-13 : 06:16:55
|
| Hi I've created an SSIS package in my test Environment. Now i'd like to put it live. I've 2 questions, 1. Should i have 2 seperate packages one test and one live ? and make change to both.2. Or should i have one package and make changes to it and then deploy it to put it live as MSDB or Files system.Thanks |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-04-13 : 06:58:06
|
I would say that is only one question  .You should have only one package.The difference between test and live are in most cases only different connection managers.I know two ways to handle that.Via config file so you can change the connectionstrings while deploying using the manifest file orchanging the connectionstrings in the job step when creating the SQL Agent job to run the package.
No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2010-04-13 : 08:58:05
|
quote:
Originally posted by rookie_sql
Hi I've created an SSIS package in my test Environment. Now i'd like to put it live. I've 2 questions, 1. Should i have 2 seperate packages one test and one live ? and make change to both.2. Or should i have one package and make changes to it and then deploy it to put it live as MSDB or Files system.Thanks
you'll have a single package which you move across environments. the automatc change of connection strings and other properties are done through package configurations. see below for examplehttp://www.sqlis.com/post/Easy-Package-Configuration.aspx------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
|
|
|
SSIS Packages & Deploment