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 |
|
Lamprey
Master Smack Fu Yak Hacker
4614 Posts |
 Posted - 2009-06-24 : 16:39:00
|
| I think I already know the answer, but I thought I'd ask anyway to see if there is a workaround.Say you want to have one config file with all the connection strings in it (say 5 of them). That way you can use that same file for all your packages. However, if a package only needs 2 of those 5 connections and you don't include "dummy" connections for the config file to populate you receive an error. Is there a way to have SSIS only load the variables that exist and ignore then rest of the values in the config file? |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2009-06-24 : 16:56:43
|
Maybe it is not the answer you want...I have learned to forbear from using config files.My packages all are based in SQL Server Agent Jobs.There in job step I am giving the credentials for each used connection manager...Webfred
No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
|
|
|
Single Config File