Re: Passing CnnStrings to Child Pkgs via variables

#1

Hello Todd,

I am a little lost as to when things get lost.

You have a parent package which gets a connectionstring value from a table
somewhere.
This is read into a variable
This variable is then used in the child package and is assigned to the ConnectionString
property of some connection manager.

Why do you need a script task? You could simply assign the values from the
ExecuteSQL Task directly couldn't you?

Does the Password="" get lost in the parent? How do you know it gets lost?

Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com

Quote:

I have a parent SSIS package with 30 children. The parent retreives
ConnectionString values from a Configuration table and, using a Script
Task, assigns them to appropriate Variables. The child packages then
pick up those values using Parent Variable Configurations.

One of the ConnectionStrings retreived (for DB2) has a
"Password=abcdefg;" tag in it which gets lost when the Script Task
assigns it to its Variable.

What makes the Script Task strip out that part of the Connection
String? More importantly, how can I keep it from doing that?

TIA

#2

Hello Todd,

But why do you use a Script task? Using configurations you can assign directly
to variable values in the parent package.

Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com

Quote:

My ultimate goal is to protect my packages from having their Source or
Destination databased moved to other servers (as has happened in the
past and will happen in the future). To do this, I set up a SQL
Database to hold Package Configurations. I have a table there that
holds Connection Strings in the 'ConfiguredValue' field.

I want the Parent Package to use its inherint Package Configurations
to retreive those connection strings for its own use. In order to also
pass those ConnectionString values on to its children, they must be in
for form of a Variable.

I set up a Script Task to populate the Variables with the value of
each respective ConnectionString. All is good, except for that one DB2
ConnectionString.

OnPostExecute of the Script, I examine the value of the variable and
find that it is missing the "Password=abcdefg" section. I know it is
reading the correct Configuration value because I can throw in garbage
like "Today=Wednesday" and THAT part shows up.

Thanks

"Allan Mitchell" wrote:

Hello Todd,

I am a little lost as to when things get lost.

You have a parent package which gets a connectionstring value from a
table
somewhere.
This is read into a variable
This variable is then used in the child package and is assigned to
the ConnectionString
property of some connection manager.
Why do you need a script task? You could simply assign the values
from the ExecuteSQL Task directly couldn't you?

Does the Password="" get lost in the parent? How do you know it gets
lost?

Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com
I have a parent SSIS package with 30 children. The parent retreives
ConnectionString values from a Configuration table and, using a
Script Task, assigns them to appropriate Variables. The child
packages then pick up those values using Parent Variable
Configurations.

One of the ConnectionStrings retreived (for DB2) has a
"Password=abcdefg;" tag in it which gets lost when the Script Task
assigns it to its Variable.

What makes the Script Task strip out that part of the Connection
String? More importantly, how can I keep it from doing that?

TIA

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: Passing CnnStrings to Child Pkgs via variables

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

Re: Passing CnnStrings to Child Pkgs via variables - 12-13-2006 , 03:38 PM

Re: Passing CnnStrings to Child Pkgs via variables - 12-13-2006 , 04:29 PM