SQL job owner

  • What is the purpose and significance of the SQL job owner setting on a job?

    I've never considered this before, but it has come up today as we have found jobs where the owner was set to a particular user account.

    How is this property supposed to be used? What is the significance of having it set to a particular account?

    Thanks.

  • The job steps execute with the security context of the job owner. However, assigning an owner does not mean that the login has the necessary permissions to run that particular job. You should always test it to make sure the job can run if the new owner is not a member of sysadmin.

  • The only people who can edit jobs is the job owner and people with SA. So unless people have a requirement to edit their jobs on a regular basis (which would kind of defeat the object of an automated process), just set the owner to SA.

  • SQLSteve (9/12/2013)


    The only people who can edit jobs is the job owner and people with SA. So unless people have a requirement to edit their jobs on a regular basis (which would kind of defeat the object of an automated process), just set the owner to SA.

    By SA, I hope you mean logins who are members of the sysadmin server role. The SA account itself should have had its name changed during the installation (but not afterwards) and should also be disabled.

  • Ed Wagner (9/12/2013)


    SQLSteve (9/12/2013)


    The only people who can edit jobs is the job owner and people with SA. So unless people have a requirement to edit their jobs on a regular basis (which would kind of defeat the object of an automated process), just set the owner to SA.

    By SA, I hope you mean logins who are members of the sysadmin server role. The SA account itself should have had its name changed during the installation (but not afterwards) and should also be disabled.

    Always disabled yes, but that doesnt mean it cant own SQL jobs.

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

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