Jobs, owners, and permissions
From: Luis F Rivera G (riveralf@hotmail.com)
Date: 06/05/02
- Next message: Luis F Rivera G: "SQL 2000"
- Previous message: Richard Waymire [MS]: "Re: NT Authority\System"
- In reply to: don tipton: "Jobs, owners, and permissions"
- Next in thread: Don Tipton: "Re: Jobs, owners, and permissions"
- Reply: Don Tipton: "Re: Jobs, owners, and permissions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Luis F Rivera G" <riveralf@hotmail.com> Date: Wed, 5 Jun 2002 07:34:25 -0700
When the owner of a job is not member of sysadmin, you
must configure a proxy account in order to execute ActiveX
Scripts or System Opertive commands.
This proxy account must has the appropiate permissions to
execute the programs that you need and access the network
resources that you need.
You can configure this account in SQL Server Agent
Propertiers - Job System - Uncheck the check box "Only
users with Sysadmin privileges can execute CmdExec and
ActiveScripting job steps" and then configure your proxy
account.
Bye;
Luis F Rivera G
>-----Original Message-----
>I've got a question concerning permissions and jobs I was
>hoping someone could help with.
>
>We have a team of application developers that are
>supporting one of our SQL Server installations. The
>application has several jobs that run on a nightly
basis.
>Depending on which developer is on call, one of them will
>be required to respond to a job failure. As far as I can
>tell by playing with SQL Server and reading BOL the only
>way to view, modify, etc a job is to be the job owner or
>have sysadmin authorities. I don't want to grant sysadm
>authorities to all three developers and if I assign
>ownership to one of them, the other two will not be able
>to access the job.
>
>I received several suggestions to create a shared account
>and make it the owner of the job. Then restrict
>permissions on that account to those required to complete
>the job.
>
>The developers are writing jobs that use ActiveX script
>steps. From what I Have been able to find it is a no-no
>to allow non-admin users the ability to call ActiveX
>scripts or execute the xp_cmdsheell stored procedure.
>
>Am I stuck with making the developers sysadmin if I want
>to allow them to monitor their jobs?
>.
>
- Next message: Luis F Rivera G: "SQL 2000"
- Previous message: Richard Waymire [MS]: "Re: NT Authority\System"
- In reply to: don tipton: "Jobs, owners, and permissions"
- Next in thread: Don Tipton: "Re: Jobs, owners, and permissions"
- Reply: Don Tipton: "Re: Jobs, owners, and permissions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|