October 27, 2011 at 4:51 am
Hi All
I have just restricted all of the developers to have read access to the DB's but there is one job which they need to execute as and when it is required.
I don't want to give them a SQLAgent role as they contain to many permissions.
I just want them to be able to execute sp_start_job but via the SQL agent section of SSMS and so they only ever see the one job in the jobs list.
Any ideas?
October 27, 2011 at 6:40 am
write a stored procedure for which you grant them exec auth.
With that sproc use the "execute as" for an account that has the auth to start the wanted job.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
October 27, 2011 at 7:25 am
Thats not a problem
But I want them to be able to start the job via the job's section under SQL agent in SSMS
October 27, 2011 at 7:39 am
I don't advise to tweak msdb sprocs. Ssms uses these to start kinderen.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
October 27, 2011 at 7:49 am
i dont want to change the procs.
i just want them to be able to see one particular job out of the list of jobs and have the ability to start it
thinking it is going to have to be the SQLAgentReader role for the time being until I get somewhere with this as i cant set all the developers as the owner of a job at the same time.
October 27, 2011 at 8:50 am
You could create a sql user and make the it job owner and:-) assign a proxy account for the job step. If they log on using that account, they can start that job. Nptpractical but it does the trick.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply