I have an app that runs selected DTS packages when a trigger file arrives.
They need to define what DTS package to run by entering the encrypted
command-line syntax, right now that is done by them running DTSRunUI.exe and
copping the generated syntax and pasting it in my app. I would rather not
make them do that because DTSRunUI.exe is not very intuitive for someone
that does not know SQL Server. Is there a way to generate an encrypted
command-line syntax using c#?

Thanks

Dan Reber

Hi

As far as I know this is not possible; effectively you are asking for the
key to the encryption algorithm.

John

"Daniel Reber" <dreber (AT) nospam (DOT) com> wrote

Do you *need the ecryption, do the packages have passwords or are the
package names sensative ?

"Daniel Reber" <dreber (AT) nospam (DOT) com> wrote

No, not the key, but method that is exposed in c# that will generate it for
me. I know that you can execute a package from c# and I was just working
how extensive the object model for DTS is exposed. I don't think that I can
though, I have not found any reference to it.

Thanks

Dan


"John Bell" <jbellnewsposts (AT) hotmail (DOT) com> wrote

We don't want the username/password exposed in a file that all of the
command-lines will be stored. I think that we found a way around it by
listing all of the packages and allowing the user to select the one that
they want.The username/password will by encrypted by my app and stored to
file along with the package that they want to execute. From there we can
create the non-encrypted commandline syntax and send it to dtsrun.exe.

Dan


"David J. Cartwright" <davidcartwright (AT) hotmail (DOT) com> wrote

Dan,

Construct your dtsrun command line and add /!Y switch at the end. This will
generate an encrypted command line without executing. This is the only way
to get encryption going. We use this approach in conjunction with
xp_cdmshell extended stored procedure so to not expose logins in files. You
can still catch xp_cdmshell sql statement with the profiler, but one would
need sa rights to do that.

Keep in mind that there is a limit to the length of dos command line in
general. The encrypted dtsrun command line is about three times longer and
you may hit this limit when you have too many parameters. We did. The step
to resolve this limitation would be keeping all parameters in a file,
encrypted if necessary. Then you would need to supply only the file
location.

Ilya

"Daniel Reber" <dreber (AT) nospam (DOT) com> wrote

Thanks Ilya, I was just about to reply stating the I found the /!Y parameter
but you beat me to it.

Dan


"Ilya Margolin" <ilya_no_spam_ (AT) unapen (DOT) com> wrote