Hi Jamie,
You wrote In your blog which I pasted below:
"I have built my packages in such a way that different packages can use the same configuration file. For example I have a "Master" configuration file that stores information that all of my packages will need (e.g. connection strings for my log files, warehouse database and metadata database). Our project makes use of many source systems so I also have a configuration file for each source system as well - that way every package that accesses a certain source system can use the appropriate configuration file. .."
How do you create a configuration for each source? I thought the concept of environmental variable is to have one configuration file in a location and defined the path to it in your system environmental variable value?
I have only one config file file for all my 9 packages and I have been having problems.
Maybe I am doing something wrong but what? Can you be more specific about this great idirect configuration?
Thanks
Omon
Putting multiple values in one configuration file is fine if you always have all targets in all packages to which you apply the configuration file to. This means if you have 5 connection strings in a configuration file, then all packages for which you use that file, must have all 5 connections. Very often this is not the case. Normally you would have x connections, but of that maybe one or two are used in every package, the rest are only used in one or two packages. So I suggest you have one configuration file for the one or two common connections, and then one file per additional connection. This gives flexibility for you to pick and choose the configuration files you require per package.
You then need one environment variable per configuration file. That is what Jamie and I use.
|||Interesting. This might solve my nightmare. I am exploring this senerio now because I have 6 connections in total but all mt packages are using 2 or 3 connections each. I don't have all my 6 connections in all my packages. I am going to add the rest connections to my packages and see what happened.
Thanks
Omon.
No comments:
Post a Comment