Re: Privilege in scheduling packages through sql agent jobs

From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 03/29/05 

Date: Mon, 28 Mar 2005 18:32:37 -0700

It means that if the programmer is not a sysadmin, the job
won't run as the dtsrun command is an CmdExec job step. By
default, the SQL Agent properties are set so that only
sysadmins can execute CmdExec and ActiveScripting job steps.
The package can be scheduled by a non-sysadmin but it won't
run unless the owner of the job is changed to a sysadmin.
The other alternative is to allow non-sysadmins to execute
CmdExec and ActiveScripting jobs and create a proxy account
which will be used as the security context of jobs not owned
by sysadmins. However, there are certainly security
implications with this. There are also other potential
issues with allowing non-sysadmins to schedule jobs - they
can't view all jobs and consequently can't take job load,
server load into consideration when scheduling jobs.
A sysadmin should probably be reviewing jobs being added and
this person can change the ownership of the job to a
sysadmin.
You can find additional information on scheduling packages,
job owners, security context, etc. in the following article:
How to Run a DTS Package as a Scheduled Job
http://www.support.microsoft.com/?id=269074

-Sue

On Mon, 28 Mar 2005 09:21:08 -0800, Maria Garcia
<MariaGarcia@discussions.microsoft.com> wrote:

>A programmer can schedule jobs through sql agent and the job step that is
>executed in the job ran cannot be ran in a package that is scheduled.When the
>programmer runs the package interactively, it runs fine. When the programmer
>attempts to schedule a package as sql agent job, the job fails. I have admin
>privileges to sql server. Therefore, I scheduled the job for the package and
>had the job run under the programmers account and obtained the following
>error:
>Non-sysadmins have been denied permission to run CMDExec job step.
>Does this mean that the programmer needs to have the system administrator
>role in order to schedule a package as a job.

Relevant Pages

  • Re: Privilege in scheduling packages through sql agent jobs
    ... > How to Run a DTS Package as a Scheduled Job ... >>A programmer can schedule jobs through sql agent and the job step that is ... >>programmer runs the package interactively, ... >>attempts to schedule a package as sql agent job, ...
    (microsoft.public.sqlserver.security)
  • Privilege in scheduling packages through sql agent jobs
    ... A programmer can schedule jobs through sql agent and the job step that is ... programmer runs the package interactively, ...
    (microsoft.public.sqlserver.security)
  • Re: Insufficient privileges (ORA-01013) "connect / as sysdba"
    ... so that's what I went to the sysadmin with. ... the package was switched to server B. ... In a recent 10.2.0.1 installation on AIX it was hardcoded and had a different ...
    (comp.databases.oracle.server)
  • Insufficient privileges (ORA-01013) "connect / as sysdba"
    ... Everything here cries "wrong group, wrong group", ... so that's what I went to the sysadmin with. ... the package was switched to server B. ...
    (comp.databases.oracle.server)
  • AS/400 and the Mac
    ... I am an AS/400 sysadmin ... and programmer. ... I have an AS/400 9406-170 in my house running OS/400 ... V5R2, I would like to be able to get a session on my Mac, as the kids ...
    (comp.sys.mac.system)