Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

granting permissions to run jobs 2

Status
Not open for further replies.

NewGuy2006

Technical User
Mar 5, 2006
11
GB

i am looking for some help around running jobs, I am a system admin and have full access to the server to run the jobs we have set up for certain processes, however we want to give other people access to run jobs without making them system admin is there anyway to allow a non system admin to run jobs?

 
i'm not 100% sure if this is the right thing to do or not, but add your users into SQL and then add those users into the public database role for msdb. this might be a little too loose security wise because the public role has execute permissions on quite a few stored procedures in msdb, so if the only thing that you want users to be able to do is start jobs (not stop, create, or delete) then create a new role in msdb that has execute permissions on sp_start_job and add the users to this role. i may be overruled by more experienced admins, but this is what i would do.
 
That will work fine. That's what we do to let our NOC folks start and stop jobs.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Hi guys,

thanks for the help I jus twanted to check with you though that the public role still stays in the users list or permit database roles but I only tick the sp_start_job for that user so thats all they can do

Is that correct?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top