May 12, 2009 at 11:47 am
How can I give the developers permission(s) to modify, execute any job that exists on the development SQL 2005 instance? TIA.
May 12, 2009 at 1:42 pm
They will probably need the "SQLAgentOperatorRole" fixed database role in the [msdb] database.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
May 13, 2009 at 9:49 am
Thank you for the reply but I've tried that already and it doesn't allow for the editing of pre-existing jobs that aren't owned by the developer(s).
May 13, 2009 at 11:10 am
Managing, executing, ect. can be granted through the SQLAgent roles. However, only sysadmin members can edit Jobs other than their own.
From BOL on "sp_update_job" (the procedure that must be used to edit a job):
Only members of sysadmin can use this stored procedure to edit the attributes of jobs that are owned by other users.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
May 13, 2009 at 12:12 pm
Thank you. I was afraid of that. 🙁
May 13, 2009 at 1:25 pm
Let us know if you find a way around it.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply