Post reply

Scheduled Jobs

  • June 1, 2010 at 1:22 pm

    #140530

    I have a number of scheduled jobs that are tied to applications. I would like to grant permission for a group of user's to manage the jobs that are associated to the defined application. They will need to be able to modify/edit, and run the jobs as needed.

    I'm not sure the best way to go about this. Do I create a proxy account or grant [run as] permissions? Any help would greatly be appreciated.

    Some assistance on how to go about setting this up would be great.

    Thanks in advance.

  • June 1, 2010 at 1:29 pm

    #1174991

    http://msdn.microsoft.com/en-us/library/ms188283(SQL.90).aspx

    Make sure you understand that these roles are concentric in relation to one another. Meaning the higher roles automatically gain access to the permissions of the lower roles. If GroupA is only member of SQLAgentUserRole and GroupB is only part of SQLAgentReaderRole. Then GroupB will automatically have access to GroupA items.

    There is no real secured way of locking down this part in I only want UserA to have access control over Jobs 1, 2 and 3; then UserB to have access to Jobs 5, 6, and 7. If a user is working with SQL Agent Jobs it is expected they know what and what not to do 😀

    Shawn Melton
    Twitter: @wsmelton
    Blog: wsmelton.github.com
    Github: wsmelton

  • June 1, 2010 at 1:36 pm

    #1174993

    Thanks, for the information. Unless I'm missing something. I have granted the user's to all three roles, they are able to see the jobs, they inform me they are unable to edit the jobs? So I'm not sure if I missed something or need to grant additional permissions to one of the roles defined.

  • June 1, 2010 at 2:27 pm

    #1175008

    This is a really stupid issue in the way they check the privileges. The issue is caused by how the username is setup in AD and how the login is defined in SQL Server.

    The process being used to validate the username/login is case-sensitive. That is, if the username in AD is all uppercase, and the login in SQL Server is lowercase - they won't match and the user will not have permissions to edit a job they just created.

    Make sure the login matches the username exactly - and this issue will be resolved.

    Jeffrey Williams
    Problems are opportunities brilliantly disguised as insurmountable obstacles.

    How to post questions to get better answers faster
    Managing Transaction Logs

Viewing 4 posts - 1 through 3 (of 3 total)

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