June 19, 2007 at 7:18 am
Robert
I don't like to encrypt the sript because there is no way to undo it. If anything happens, I have no way to debug it.
My problem is I have a sql server job but each month it runs on different day depending when the user is ready. I don't want the user to go to SQL Server to start the job (that means I have to give him the SA permission.) and that means he will call me every month to start the job for him which I don't like it either.
So I am thinking if I can put out a bat file in the window directory, and the bat file will start the job, the user can do it anytime. He has administrative right for that window box. But I just don't like to put in SQL Server user Id and password in the bat file.
So if the job owner is different from the user sign on ID and it is window authentication. I can use /E to run the job.
June 19, 2007 at 7:20 am
Benoit,
Being a project manger, you know a lot more about DTS package and SQL server than some of the SQL Server developers I know. My company will never let a project manager to write a DTS package.
June 19, 2007 at 8:32 am
The /Z switch is only for encrypting the command line parameters, such as user ID and password, that you are passing in to the DTSRun executable. Nothing else gets encrypted.
The /E switch will use the windows account of whoever is logged in tot he machine, so the person would still need adequate permission to execute the DTS Package. You can use the /E switch and hard code a specific Windows account in Windows task scheduler and then just give everyone rights to execute the scheduled task. You don't have to have an active schedule for a scheduled task, the user can simply go in and right click on the task and click Run (or execute, I forget which).
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply