SQL 2000 on Windows 2000 Domain Controller
I know there are various threads on this subject, but could somebody
help me out with the following?
One of our developers had scheduled a DTS package, and it failed with
the "Non-SysAdmins have been denied permission to run CmdExec job
steps. The step failed"
Following some previous replies, I changed the job owner to 'sa' and
the job worked! However, the developer can't now see the job and
can't therefore view the job history to see if it succeeded or not.
Can anyone:
(1) Point out the pros/cons of setting the job owner to 'sa' as
opposed to setting up a SQL proxy account to do the job?
(2) Point me in the right direction of allowing the developer access
to view the job (and edit it if necessary)?
Thanks for your help.
I know there are various threads on this subject, but could somebody
help me out with the following?
One of our developers had scheduled a DTS package, and it failed with
the "Non-SysAdmins have been denied permission to run CmdExec job
steps. The step failed"
Following some previous replies, I changed the job owner to 'sa' and
the job worked! However, the developer can't now see the job and
can't therefore view the job history to see if it succeeded or not.
Can anyone:
(1) Point out the pros/cons of setting the job owner to 'sa' as
opposed to setting up a SQL proxy account to do the job?
(2) Point me in the right direction of allowing the developer access
to view the job (and edit it if necessary)?
Thanks for your help.