Comments on: Creating a REAL SQLAgentReaderRole

By: Mark

Mark — Fri, 20 Jan 2012 16:34:05 +0000

If you don’t like the idea of a role in your system database, you could just grant the sqlagentreader role to a group like ‘TheDevelopers’ and then deny execute on those procs to that group or to individual logins. This approach is not ideal either. You have to alter privilges on the system sp’s for every group or login but technically speaking you do not have a role in your system database… but you don’t have the advantages of a Role which is easy to grant to a user(s).

A better idea… MS SQL Server: Please provide an Agent Reader Role!!

By: Dave

Dave — Tue, 11 May 2010 17:50:01 +0000

Thanks — this seems to be just what I was looking for.

Are you still using this role as defined above? Have you found any gotcha’s?

By: Ernest

Ernest — Thu, 11 Mar 2010 21:26:55 +0000

Perfect. Had to do the same thing (Devs are not allowed to create jobs on prod systems so can’t use sqlagentreader).

By: Murali

Murali — Sat, 24 Jan 2009 10:21:03 +0000

This is gud workaround. Thanks.

By: SQL Server Central

SQL Server Central — Thu, 22 Jan 2009 13:23:42 +0000

[...] Creating a REAL SQLAgentReader role [...]