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 |
|
Grouse219
Starting Member
2 Posts |
 Posted - 2007-04-09 : 10:34:53
|
| I have an application with 4 enviornments, test, dev, qa, prod - each with dedicated databases - some on seperate servers - some on same server seperate instance, some in same instance.Plan to develop one SSIS Project with multiple packages and use DTSConfig files to store the connection strings.Question one:Where to store deployed packages - in SQL (msdb) or File SystemQuestion two:Where to store DTSConfig files - default directory or dedicated SQL Configuration directory.Question three:Retain one DTSConfig file per package or merge the connection strings into one global DTSConfig file per enviornment.I know there is no right or wrong answer to any of these questions - just looking for ideas.My plan (as of now)- Deploy the SSIS packages to SQL Server (stored in msdb) for each Server- Create dedicated folder (F:\SQLConfigs) to store DTSConfig files for each server- Manually combine the each packages DTSConfig into one global DTSConfig for each enviornment. Use this DTSConfig when configuring job steps in SQL Server Agent.Thanks for your ideas. |
|
|
stephe40
Posting Yak Master
218 Posts |
Posted - 2007-04-17 : 15:11:14
|
| This may not be the case if your DBA gives you access to deploy packages directly into MSDB. For me, I get ansy whenever someone points a Microsoft deployment wizard at one of my system databases. I would perfer if packages were stored on the file system. That way you do not require DBA involvement when you want to update your package. You just need the proper file system access.- Eric |
 |
|
|
influent
Constraint Violating Yak Guru
367 Posts |
Posted - 2008-09-12 : 19:02:26
|
| Is there actually a way to store a package in msdb in SQL Server but have a dtsconfig file??? |
|
|
|
|
|
|
SSIS Design Question - best pratices