Re: Rights to execute jobs?
- From: "Chris Wood" <anonymous@xxxxxxxxxxxxx>
- Date: Tue, 14 Aug 2007 10:42:27 -0600
Brian,
Are you running SQL2000 or SQL2005? It looks like 2000 because you mentioned
EM. We, just moving up to SQL2005, have a similar problem and have created
an SQL login to run jobs. A Windows group cannot own a job and so, as you
say, cannot create jobs with other owners unless it is a sysadmin. If
running with a created SQL Login seems okay to you I can detail the
permissions that we are giving.
Chris
"Brian Laws" <BrianLaws@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AA330618-DB8C-48E9-A43B-BCD1C9053EF1@xxxxxxxxxxxxxxxx
Hello!
We're trying to lock down our environments (dev, qa, uat). One requirement
is that a group needs to not be an admin but still be able to execute any
job. I've looked and looked, but I haven't yet been able to find a good
resource for job execution permissions. I know that a job owner can
execute a
job, but our standard is to make all jobs owned by SA. So, can somebody
outline what permissions are required in order for a non-sysadmin to run a
job not owned by themselves? Is that possible? It occurs to me that I may
be
able to do this by making a stored proc to execute a passed-in job name.
Since procs execute anything inside it (only permissions needed are to the
proc itself), this may work. I'd like to avoid this, though, and let them
run
through EM.
Thanks for the help!
.
- Prev by Date: Re: SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- Next by Date: sysprocesses
- Previous by thread: Re: Users , Web Application and SQL Server back end - Beginner Questio
- Next by thread: Re: Rights to execute jobs?
- Index(es):
Relevant Pages
|