November 25, 2013 at 9:54 pm
As mentioned in BOL SQLAgentReaderRole members are just able view the list of all available jobs and job schedules and their properties. Surprisingly when i add a user to this role the user is then able to start/stop the SQL Server agent service from SSMS as well as from Configuration manager. Is it expected behavior or some thing is wrong. I did not get any reference that members of SQLAgentReaderRole can manipulate the agent service status. Any feedback on it please?
DBDigger Microsoft Data Platform Consultancy.
November 26, 2013 at 12:28 am
I don't think this is the expected behaviour.
Are you sure the user doesn't have other permissions?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 26, 2013 at 12:31 am
I guess the user has some other permissions more than SqlAgentReaderrole...Can you double check it?
Regards,
Kumar
November 26, 2013 at 1:52 am
AShehzad (11/26/2013)
I have created a new login with public server role. Just added it SQLAgentReaderRole in msdb. Again i am able to start/stop the agent with this login. So could any one confirm this on his machine as well please.
I tested it on my machine.
Created SQL user with public server role. Mapped it to a user in MSDB database with public, SQLAgentUserRole and SQLAgentReader role in MSDB and chose MSDB as default database (with dbo as default schema).
I logged in as this user and I could not stop or start SQL Server Agent, as expected.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply