Comments on: SSIS 2008 Package Configuration Issue

By: Micheline Leichtman

Micheline Leichtman — Sun, 04 Jul 2010 17:01:04 +0000

Good information on here. Thanks!

By: Todd McDermid

Todd McDermid — Wed, 28 Oct 2009 22:49:39 +0000

One other way to solve this issue is to not collect all of your connections’ strings into a single configuration file. Several of the people most familiar with configuring and deploying SSIS packages recommend that you store ONE connection manager’s connection string per configuration. That way, you can pick and choose which configurations you need for a particular package – as it’s a one-to-one relationship between configuration files and connection managers. This also means that if you need to change a connection, you (still) only have one place to change it – and you no longer receive any warnings OR errors.

By: Jake

Jake — Wed, 28 Oct 2009 22:29:55 +0000

It’s not really much to manage since we only have 6 or 7 databases that we connect to. So that’s one file for each connection that is stored in the same directory on each of our servers (dev/test/prod). My goal was to make it as easy as possible to move a large number of packages from dev to test to prod. With this set up there are no changes that need to be made to the packages when they are moved to different servers. I can simply copy and paste them.

I didn’t think too much about storing them in a SQL table. I guess I could have just have one configuration file with the connection to that environment’s configuration server/table. Then in that table I could store all the other connections in the configuration table….so many possibilities.

By: bsullins

bsullins — Wed, 28 Oct 2009 19:31:23 +0000

Hmmm…interesting, that seems like it would be a lot to manage. Have you considered storing them all in one SQL table and using separate config filters for each connection?

My goal with this was to create a package template that would automatically apply all the appropriate connections w/o any additional work by the developer other than following the naming convention for their connection manager…

By: Jake

Jake — Wed, 28 Oct 2009 19:22:54 +0000

I ran into this error as well when moving to 2008 ssis. My solution was to create a seperate config file for each connection string my packages might need. I only add the config files I need to each individual package. The pros are that it was simple to setup and I can still easily update one file when we have a server move. The con is that I have one file for every connection instead of just one file containing all my connections.