January 28, 2008 at 1:03 pm
I have a user, and added it to the SQLAgentUserRole. BOL says:
[font="Courier New"]Action . ............. Operators ........... Local jobs (owned jobs only)
Create/modify/delete ....No ................... Yes[/font]
Doesn't this mean it should be able to create a job ??
January 28, 2008 at 6:26 pm
I created a sql login/user with SQLAgentUserRole in msdb. This user can create job. What did you get?
January 29, 2008 at 1:10 pm
I get permission denied on 'sp_add_job'
Edit: My Bad ........ The user was also a member of TargetServersrole, which must have lower permissions than SQLAgentUserRole, so it was being restricted. I took it out of TargetServersrole and it worked. I used TargetServersrole in SQL 2000 as a workaround to give a couple of power users extra permissions, and I guess I left it there after converting to 2005. I don't think I need it in 2005 now with these new roles.
March 10, 2010 at 11:55 am
ya you create new jobs and schedules, and can manage only those jobs and schedules they create.
you can't create operators and proxies, If you need to assign an operator or proxy to a job step, it must have already have been defined.
you can't able to see the properties of other local jobs or multi server jobs as same as you can't able to see and modify the job history.
Regards!!
chreddy
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply