Post reply

Restrict Agent Jobs

  • May 16, 2007 at 8:54 am

    #195738

    Hi,

    How to restrict my Agent Jobs being run by other developers?

  • May 16, 2007 at 9:23 am

    #706847

    Deny EXECUTE permission on sp_start_job in msdb.  Make sure developers aren't sysadmins.

    Greg

    Greg

  • May 16, 2007 at 10:27 pm

    #706996

    There is no need to deny access - if you are not a sysadmin you can only see your own jobs anyway.

  • May 18, 2007 at 7:12 am

    #707425

    And if the other developers are sysadmin, you can run the Deny statement, but they can just undo it later on.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • May 20, 2007 at 5:04 pm

    #707710

    You cannot deny a sysadmin access to any database object - they are allowed to see and doing anything they see fit. Hence, even if you use the DENY statement in an attempt to stop access to a table to a user who is a sysadmin, that will not affect their access at all.

  • May 22, 2007 at 1:47 am

    #707979

    Surely your developers are not SysAdmins in the first place. I can understand on a test box perhaps but not on a production box. I have manipulated the TargetServersRole in the msdb database to restrict our Application Support team from specific jobs. It may be worth your while look at that. Rgds Derek

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply