November 17, 2013 at 7:59 pm
SQL Server 2012, some jobs are centralized from another server running SQL Server 2008 R2.
I'm having a problem getting jobs to run under the account I want. I've changed security settings and the account under which jobs previously ran no longer has sufficient privileges to run the jobs. I created a domain account and want to use it for all jobs.
I've set the new account as the MS Agent startup account on all servers. The job owner is in the sysadmin role on all servers. I've restarted the services. The jobs stubbornly continue to execute under the old account. Where else can I look to adjust the job runner account? Or, is there a way to discover why the jobs persist to run under the old account?
November 18, 2013 at 4:21 am
Check in the job step the run as option and see if the account is in the proxi used by the run as...
November 18, 2013 at 4:33 am
If the job executes a stored procedure it is also possible that in the code of the stored procedure a "EXECUTE AS" is defined.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply