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

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 (AT) discussions (DOT) microsoft.com> wrote

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:

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.
If the server from which you get the encrypted connection info is able to be
connected to then we can still store it in there. You need to encrypt and
then decrpyt from here though right.

OK what about this for an option.

You pass in the connection info to the package on the cmdline using DTSRun.
You tell DTSRun to encrypt the command.

Would that work?


--


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com


"lmcphee" <lmcphee (AT) discussions (DOT) microsoft.com> wrote