May 4, 2010 at 9:57 am
Hi all
i have a question about the accounts that SQL jobs are owned by. My current understanding is that jobs are usually owned by the SQL agent service account. This account is placed into a windows group at the time of install, and that group has sysadmin permissions in my instance.
Now maybe this is setup incorrectly, as it raises questions with me. Specifically what would be the need for proxy accounts on individual steps within the jobs if the account being used is already a sysadmin.
I am just looking for some advice around this, and standard ways to setup job ownership.
Thanks
May 4, 2010 at 10:14 am
There is a difference between ownership and execution context. Typically the jobs are not owned by the SQL Server Agent service account. They are owned by whowever created the job in the first place. So unless folks are logging in as the SQL Server Agent service account (which they shouldn't be doing), the ownership will default to the job creator.
If the job creator is a member of the sysadmin fixed server role, then the job step will execute, by default, as the SQL Server Agent service account. You can set up a proxy to run jobs, and you'll need to do so if the job is owned by an account that is not a member of the sysadmin fixed server role. To see how to do this, take a look at CREATE CREDENTIAL in Books Online.
K. Brian Kelley
@kbriankelley
May 5, 2010 at 7:04 am
thats great and has cleared it up for me thankyou
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply