Indirect configurations ROCK!

Hi Jamie,

You wrote In your blog which I pasted below:

"I have built my packages in such a way that different packages can use the same configuration file. For example I have a "Master" configuration file that stores information that all of my packages will need (e.g. connection strings for my log files, warehouse database and metadata database). Our project makes use of many source systems so I also have a configuration file for each source system as well - that way every package that accesses a certain source system can use the appropriate configuration file. .."

How do you create a configuration for each source? I thought the concept of environmental variable is to have one configuration file in a location and defined the path to it in your system environmental variable value?

I have only one config file file for all my 9 packages and I have been having problems.

Maybe I am doing something wrong but what? Can you be more specific about this great idirect configuration?

Thanks

Omon

Putting multiple values in one configuration file is fine if you always have all targets in all packages to which you apply the configuration file to. This means if you have 5 connection strings in a configuration file, then all packages for which you use that file, must have all 5 connections. Very often this is not the case. Normally you would have x connections, but of that maybe one or two are used in every package, the rest are only used in one or two packages. So I suggest you have one configuration file for the one or two common connections, and then one file per additional connection. This gives flexibility for you to pick and choose the configuration files you require per package.

You then need one environment variable per configuration file. That is what Jamie and I use.

|||

Interesting. This might solve my nightmare. I am exploring this senerio now because I have 6 connections in total but all mt packages are using 2 or 3 connections each. I don't have all my 6 connections in all my packages. I am going to add the rest connections to my packages and see what happened.

Thanks

Omon.

Indirect Configuration problem

I'm having a problem with indirect configurations on my client's machine.

I've created a package that uses an xml configuration file (.dtsconfig file) that is pointed to by an environment variable. I have this package running on my machine using Windows XP and on my test machine that uses Windows Server 2003. When I set it up on my client's test machine also running Windows Server 2003 the package doesn't recognize the configuration and tries to use the values that it was originally programmed with on my development machine.

I installed the packages the same on both test servers including adding the appropriate environment variables. Is it possible there is something wrong with the environment? I haven't checked the various service pack levels on the two machines. I know that I keep my test machine up to date. I'm not sure about my client. Are there any known issues like this under specific service packs? Or am I just probably missing something glaringly obvious?

Thanks,

Jeff

Having an xml config file point to an environment variable is somewhat redundant, you could just have the environment varialbe as a configuration. Regardless, I've had issues with packages not recognizing new environment variables before. I'd try restarting the machine first.

|||

That was it. Thank you.

Jeff

sql

Indirect Configuration in SSIS

Hi,

I need to configure my package using SSIS Configurations. When I opened SSIS Configuration wizard, press ADD and selected Xml Configuration, I found two options.

One being : Specify configurations directly.

next : config location is stored in env variable.

How to use the second option?[ env variable]. Say I want to configure my connection string for my destination database [ OLEDB Destination Component]. How to do that using second option.

Thanks

Kishan

You first need to create your configuration file so go for option 1.

Once you've created it, create an environment variable whose value is the path and filename of the config file.

Go back into your configuration and edit it to use the environment variable rather than the config file.

And that's it!

In case it helps: SSIS: Indirect configurations ROCK!

-Jamie

|||this link might also help: http://dotnetjunkies.com/WebLog/appeng/archive/2006/05/30/indirectconfigpackagessis.aspx