SQL Undercover Agent Double Oh No 7

So you are getting 1337sauce with your security, removing nubs from their previous sysadmin roles to public with explicit permission to objects like you should…maybe even locking down developers since they are just that and not admins?

You may run into a case where a developer needs to access the SQL Agent but when they use Management Studio its….gone?

Right, cause you locked them down hard. Very nice.

Youll need to give them a mapping to msdb and put them in the SQLAgentOperator Role. This should be enough privelages on a development server for those code monkeys.


Leave a Reply

Your email address will not be published. Required fields are marked *