November 23, 2010 at 12:17 pm
Currently we aren't exactly best practice. I am trying to fix us up. I have a question about that. Is it best practice to create an AD account and give it permissions on the server to run jobs like maintenance plans or should I create a sql user on the instance locally for this kind of task? I know it is best practice to use AD accounts for the services but what about the jobs inside?
November 23, 2010 at 1:14 pm
I generally use a local account for the services, and an SQL account for activity inside the databases. I've had a server lose its connection to the AD server while trying to run routine maintenance, and create a mess out of the whole thing because it couldn't get the security tokens it needed. On the other hand, it's only come up once for me, and it's kind of "closing the barn door after the horses are gone" because of that.
- 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
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply