I have more than 20 packages, most of them have similar connection strings. I would like to use one config file to include all distinct connection string in all packages and share this configuration file in all the packages. The purpose to do this is to reduce the time for setting. But I can setup to use the shared configuration from BI development studio. But when I rebuild the project it gave me error. If I remove to share a single configuration the build will success. So how to fix the problem? ThanksHelen

when you create a configuration file with a connection string , then all packages which have this configuration file should have that connection exists. forexample you created a connection string for connection manager object,let's name it as CnnMgrCnString . then all packages that have this configuration file should have CnnMgrCnString inside. http://www.rad.pasfu.com

Hi All I'd like to add to Reza's comment is that they all must have the same SSIS VARIABLE SCOPE as well what i do is to have 3 main config XML files 1- FolderConfig (for each Package) 2- SourceConfig (for each Package) 3- DestinationConfig (for each Package) 4- Emailand SMTPConfig (for each Package) then depending on my design and the customers request set my config xml files i.e. one of the customers had only one destination table they have over 100 Package that hin the same final destination table and for error handling in the package, the package sends a error EMAIL to the same SMTP server to one user admin only (customers request) so i only have One "Emailand SMTPConfig" xml config files that is used by all packages , (I have it in a folder called GlobalConfigXMLFiles) One "DestinationConfig" xml config files that is used by all packages , (I have it in a folder called GlobalConfigXMLFiles) so when calling my package within a SQL JOB i pas the 2 XML files to the package from the "GlobalConfigXMLFiles" Sincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

one last thing is that if you are using a XML config file to make a connection string that is OK BUT the question is the files name (if source is a file ) or maybe the SQL DB name (if source is a DB) can not be in the same XML config file unless they are all pointing to the same source (or maybe destination) format my question is that you sources have different names and are located in different location how are you going to solve that by only having one XML config file??????Sincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

Hi All I'd like to add to Reza's comment is that they all must have the same SSIS VARIABLE SCOPE as well what i do is to have 4 main config XML files 1- FolderConfig (for each Package) 2- SourceConfig (for each Package) 3- DestinationConfig (for each Package) 4- Emailand SMTPConfig (for each Package) then depending on my design and the customers request set my config xml files i.e. one of the customers had only one destination table they have over 100 Package that hit the same final destination table and for error handling in the package, the package sends a error EMAIL to the same SMTP server to one user admin only (customers request) so i only have One "Emailand SMTPConfig" xml config files that is used by all packages , (I have it in a folder called GlobalConfigXMLFiles) One "DestinationConfig" xml config files that is used by all packages , (I have it in a folder called GlobalConfigXMLFiles) so when calling my package within a SQL JOB i pas the 2 XML files to the package from the "GlobalConfigXMLFiles" Sincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

If one of the packages uses Connection Managers 1, 2, and 3, and another uses Connection Managers 2, 3, and 4, AND your SINGLE XML congfig file has all four Connection Manager Connection Strings configured, then you will get errors and warning when you run because the first package does not use #4 and the second package does not use #1. Another approach is to put all your Connection String Configurations is a SQL Server database, ONE Connection String per "Filter" then configure each package to use ONLY the entries it needs. Read about this methodology in my blog here.Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.