If the connection info is stored in SQL Server and the connection info is
the info you need to connect to the server then that isn't going to work.
connected to then we can still store it in there. You need to encrypt and
You pass in the connection info to the package on the cmdline using DTSRun.
"lmcphee" <lmcphee@discussions.microsoft.com> wrote in message
news:21F878D7-A98C-492D-B78A-5FB3CF47B37C@microsoft.com...
> Wherever the connection info goes, it would have to be encrypted. It could
> be
> stored in SQL. So have to write it encrypted, and then retrieve it with an
> encrypted procedure, limiting access to the procedure?
>
> LMcPhee
>
> "Allan Mitchell" wrote:
>
>> You can store the configuration information external the packages say in
>> a
>> DB table or an ini file and use that. Your packages will look for the
>> info
>> in here and configure themselves
>>
>> --
>>
>>
>> Allan Mitchell
>>
www.SQLDTS.com >>
www.SQLIS.com >>
www.Konesans.com >>
>>
>> "lmcphee" <lmcphee@discussions.microsoft.com> wrote in message
>> news:AB38A3AD-C9B9-4FE1-920C-0A2FDD022510@microsoft.com...
>> >I have a set of pkgs I want to execute from a "master" pkg. These are
>> >for
>> > distribution to a customer who wants SQL authentication. We can't have
>> > the
>> > PWD unencrypted in the master pkg, so what params do I use for
>> > LoadFromSqlServer in the master pkg to create and execute the child
>> > packages?
>> >
>> > Can I define a Connection object in master pkg with SQL authentication
>> > and
>> > same UID/PWD as children and somehow use that?
>> >
>> > LMcPhee
>>
>>
>>