I currently have multiple (parent and child) packages using the same config file. The config file has entries for connections to a number of systems. All of them are not used from the child packages. Hence, my child package throws an error when it tries to configure using the same config file because it can't find the extra connections in my connection collection.
Does anyone have any ideas on the best way to go about resolving this? Is multiple config files (one for each connection) the only way?
Sachin
I have found that one file per connection is ultimately the best way to go. You may be able to have more than that, if you are sure you will always use the same configurations at the same time, but that seems to be more useful when you have some variables, perhaps a couple of file paths used for all of your packages to do logging or check pointing, but you need to be careful of not falling into the same trap again of over grouping. Keep it at the lowest level you can, it is just more flexible I have found, and copes better with change as well. (Deleted Post?)
|||Darren
Looks like that might very well be the way to go then. I wonder if there is any way to include other config files into a single file, but that's for another day.
Thanks for the prompt reply.
Sachin
|||Nice idea, support for XML Inclusions (XInclude) would do it (http://www.w3.org/TR/xinclude/).
One for MS Connect I think - http://connect.microsoft.com
No comments:
Post a Comment