alpha0mega


Hi,

I am unsure if i am managing my connections in the correct way... but as it stands we have them in a .dtsConfig file that each package references in order to get the relevant details..

This is working fine, except that in total our ETL project uses 6 different connections, and none of the packages utilise all 6.

This leads to an error message upon opening up EVERY package stating that there are connection strings in the .dtsConfig that are unused, yeah, thats the idea!

The way i have gotten around this, is to just include all 6 connection managers in every package, but my question is, is there a better way to achieve this same result

are we going about this in a bit of a cackhanded way

any incite would be useful..

Best Regards

Chris




Re: Unused Connection Managers

Rafael Salas


A work around could be to use SQL Server based package configuration; you will have an entry on the config table for each configuration.






Re: Unused Connection Managers

alpha0mega

I don't understand how this would work...

would i not need to provide a connection to get the connection






Re: Unused Connection Managers

Eric Wisdahl

In short, yes. You would have one config setting that would be set independent of the rest, usually as an environment variable. If you search the forums there are plenty of threads on this subject already...






Re: Unused Connection Managers

jwelch

Or you could use 6 XML config files, one per connection. It means you have a few additional files to manage, but you don't have to put all the connection managers in every package.




Re: Unused Connection Managers

Danny Crowell

Chris, one way to handle this is to create 6 configuration files with 1 connection in each. Each package uses only the configuration files that apply. This prevents the annoying warnings from BIDS and allows us to use configurations in a modular way.






Re: Unused Connection Managers

alpha0mega

ok, thanks for the help all

i think for now ill stick with all the connections in each package, and then when i finally deploy it go with the configuration table..

thank you!