September 1, 2011 at 1:43 pm
I'm editing someone else package. It has master ssis package that in the package it also calls many other child packages.
We have a configuration file for the master package in which it defines one of the connections like this:
</Configuration>
- <Configuration ConfiguredType="Property" Path="\Package.Variables[User::conn_ReaFilePath].Properties[Value]" ValueType="String">
<ConfiguredValue>\\sql10\product</ConfiguredValue>
</Configuration>
This user connection variable is defined in the parent pacakge which is the same as in the configuration, and also there is the same name variable defined in the child variable. but in child variable it points to another file like\\sql10\test, and the child package has package configration set to use package variable.
My question is when the child package run, which connection string it uses?
I guess because the child package uses its own configuration which is the package variable, so it uses the \\sql10\test, is that correct?
To fix this, to point to production, shall i just change it to use the same configration file as parent package?
Thanks
September 2, 2011 at 10:28 am
If I understand you correctly the Child Package should be using the same value as the parent package. My understanding is that the master package has the variable conn_ReaFilePath which is set by a package configuration. Then the child package has a ParentVariable configuration that sets the value of the Child Package variable conn_ReaFilePath to the value in the parent variable.
Configurations are always applied over the values set in the package during design time.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply