April 15, 2014 at 6:22 am
I have read here and elsewhere that it is best practice to set the job owner to the sa account, mainly because if the job is owned by a domain user and that user leaves the job will no longer work.
But what if I have a job that needs to be managed by a non sysadmin user who is connecting with their domain account? Is my only option to make them the owner of the job and just deal with the consequences if their account is disabled in future?
Also, if their account is locked will the job be able to run?
April 15, 2014 at 10:17 am
Also, if their account is locked will the job be able to run?
Correct if their account is removed or locked the job will fail. We set all of our job owners to SA nightly (We have a job to do this). Usually we do not want someone editing any jobs other than DBAs in production.
- Tony Sweet
April 16, 2014 at 6:59 am
Thanks Tony, that's what I thought. I was just hoping that maybe there was a way to delegate job management without giving sysadmin rights but I guess there is not.
April 16, 2014 at 7:38 am
This was reposted this morning. It may help http://www.sqlservercentral.com/articles/Stairway+Series/72460/
- Tony Sweet
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply