December 2, 2011 at 10:36 am
I have a project that has several packages. Some connection strings are the same, some are different.
Variables are different too.
Is it good to have configuration file for them separately, or share one same configuration file?
If one configration file is good, how can I combine them together?
Thanks
December 2, 2011 at 11:10 am
I doubt you will be able to combine them. The reason is that if a package doesn't have a connection or a variable you will get at least a warning and perhaps an error when it tries to set the value.
I prefer a hybrid approach. For connections that should be the same accross all packages I create one config file and set it to read-only, then I force all the packages to use it. Keep in mind that all packages need to have the same connection name.. If you have package specific configs I would probably keep them separate and consider how bad you need them..
CEWII
December 2, 2011 at 11:16 am
You can combine them, but you will get a warning for each connection that doesn't exist in the package. I prefer to use SQL Server Configurations and store them in a single table. Then I use an indirect configuration for the connection string to the configuration database. Then I can reuse the connection strings I want in each package.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply