February 23, 2011 at 7:58 am
I am looking for best practices of how people configure job owner for the various jobs executed on SQL Server 2005. It seems like most places I go the owner is whoever the old DBA was, and the job steps are executed by the SQL Service Agent Account or a Proxy Account or something elese. My question is who should the owner of a job typically be? A Domain account, the service account, other?
February 23, 2011 at 9:18 am
I always set up (or get set up) a domain account that's specifically configured for running these jobs. Minimum permissions needed, and definitely not my own account if I can help it.
Otherwise, if you have to replace a DBA, you can't deactivate the account or your jobs stop running. That's no good.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
February 23, 2011 at 9:33 am
Thats where I have been moving towards. Creation of accounts that are "Finace_Jobs", "Engineering_Jobs", etc. But I started considering the idea of trying to utilize the proxy accounts more rather than giving the job owner account permissions. It seems like there are three levels of security questions when setting up a job.
1. Job Owner.
2. Job Steps Executed As User
3. Using Proxy Accounts
I was trying to figure out how others did it to come up with a good standard. So do you give permissions ot the job owner and run all the steps as that owner as well? Do you find yourself ever using proxy accounts, or do you just setup the job owner with the needed privs?
Thanks.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply