April 7, 2008 at 8:49 pm
I am deploying a couple of jobs that have one step which runs a dts package. In the past, I have used the /~Z option with the full set of parameters encrypted in one long string. I typically create this string either by using dtsrunui or just scheduling the dts package in a job and adding other none dts steps after the job is created. What I do not like about this approach is that each time the dts package changes, you need to update the job because the /~Z option uses the version guid of the dts package and that changes with each save. So I was hoping to encrypt the user password and package password individually, leaving the name and other parameters un-encrypted but have not been able to figure out to do that. Anyone else tried to do this? What am I missing?
Mark
Mark
April 9, 2008 at 9:53 am
I always use dtsrunui to generate the encrypted DTSRUN string. If you select just the package name rather than selecting a specific version, the package will always use the latest version. Put that string in a job step and the job will always run the latest version of the package so you won't have to regenerate the DTSRUN string after every package modification.
Greg
April 9, 2008 at 10:38 am
Thanks. That would solve the problem.
I also found through another sites discussion thread that by checking the SQL Server 7.0 format check box under command line in DTSRUNUI, it provides the individual parameters encrypted when you click Generate which is what I really wanted. I chose this option so that some of the information on the command line is readable. I like being able to see what the DTS package name is and what the defined login is when troubleshooting.
I appreciate the response though!
Cheers,
Mark
Mark
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply