How to use multiple configuration files?

Hi everyone,

How to change dynamically the connection properties for a DTSX?

Imagine that you launch a SSIS and under a several rules the same connection is reused with four or five different databases.

I know that I can attach a configuration file or more than one but how to tell to SSIS which use in every moment?

Thanks in advance and regards,

enric vives wrote:

Hi everyone,

How to change dynamically the connection properties for a DTSX?

Imagine that you launch a SSIS and under a several rules the same connection is reused with four or five different databases.

I know that I can attach a configuration file or more than one but how to tell to SSIS which use in every moment?

Thanks in advance and regards,

Do you mean you need to execute the same package multiple times but assigning different connection strings to connection managers on every execution?

|||Assign the InitialCatalog property of your connection object to a variable using expressions, and then make a Script task that sets the variable property depending on your condition.

I think it'd be better if you could just set one username/password for all databases so that you'll only need one config file for them all. This is only a problem if the passwords are all different (which I suspect them to be).|||Thanks for that.

How to use deployment utility using a single package configuration file

Hi,

We are trying to create a deployment utility for a solution. The issue we are facing is, we are using a single package configuration file and when we try to build the solution to create the deployment utility, the build process fails saying that the package configuration file already exists. THe reason for this is while trying to build, the utility copies the configation fiel for the packages, it copies for one, but for the second onward, when it tries to copies, it fails saying the file already exists.

Any idea how to overcome this, or else any suggestions how to perform the similar steps to create a deployment utility for a solution in which the packages share a single package configuration file.

Any suggestion would be really appreciated.

Thanks in Advance,

Manish Singh

This is a recognised problem with the deployment wizard and will, I'm sure, be fixed at some point.

In the meantime, you may want to look at alternative methods such as XCopy. Another alternative may be the WiX toolset, I have had a lot of success with that.

-Jamie

|||Thanks for the post Jamie , but could you let me know how XCopy or WIX Toolset works

Thanks in Advance
Shailesh|||

XCopy basically means using the command-line tool xcopy.exe to manually copy the files.

Using WiX is far more involved and is a much igger subject than can be answered in a single post I'm afraid.

-Jamie

|||Thanks again Jamie , but i found a better option to use the shared configuration file . U can actually create an environment variable and set the path of the Configuration file . Which you could indirectly reference in each and every package .

There is another workaround , where you can manually create the manifest file . This approach allows you to call one configuration file in another :: havent checked this part though .

Thanks for your response
keep up the good work

Regards
Shailesh|||

Shailesh Chaudhary wrote:

Thanks again Jamie , but i found a better option to use the shared configuration file . U can actually create an environment variable and set the path of the Configuration file . Which you could indirectly reference in each and every package .

Shailesh

This is called an Indirect Configuration. I am a big fan.

Indirect configurations ROCK!
http://blogs.conchango.com/jamiethomson/archive/2005/11/02/SSIS_3A00_-Indirect-configurations-ROCK_2100_.aspx

-Jamie