May 6, 2015 at 1:12 pm
Looking for an article that explains how to set security for SQL Agent Jobs to allow developers to view and edit the jobs without being sysadmin.
It would be good to show how this can work with system security, or with custom security changes.
Challenge: probably a second article, but can you allow dev A to edit some jobs and dev B to edit others?
August 24, 2015 at 4:42 pm
I know of a simple way to do this by overriding the stored proc that updates the agent jobs and then impersonates the SQLAgentOperatorRole with the Execute As.
Would something like this make a reasonable article on this topic?
August 25, 2015 at 9:58 am
Does this limit editing of the job itself? I was looking for a way to let Dev A edit jobs 2 and 3, b but not 1 and 4.
It does sound like a good article, but not sure it meets this need.
January 5, 2016 at 9:13 am
Hello, I usually do this by creating a credential and then assign a proxy to the job step. Is this what you were thinking of? Or were you looking for something a little more technical?
January 5, 2016 at 2:19 pm
dbgrl93 (1/5/2016)
Hello, I usually do this by creating a credential and then assign a proxy to the job step. Is this what you were thinking of? Or were you looking for something a little more technical?
This is probably good. Maybe room for another, more complex piece, but a simple one that shows how to allow a user to view and edit a job.
February 9, 2016 at 5:47 pm
bump
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply