wolfkillj (6/19/2013)
What does your job do (i.e., what kinds of steps - T-SQL commands, execute SSIS packages, etc.)? Do all steps happen on the same server\instance? What is the service account for the SQL Agent service?
T-SQL jobs running a stored procedure that restores a database.
SQL Server Agent is running under a domain account (plain vanilla) with sysadmin access. That same account owns the jobs in question.
Greg Edwards-268690 (6/19/2013)
And are you sure no one logs into SSMS as SA?Then executes the job?
Yes, I am sure no one is logged in under SA and running these jobs. How do I know this? I'm the one running the job.
David Benoit (6/19/2013)
Is there any correlation to who is running the job and this occurring? Can you run a trace and get more details for all the manual executions of this job and see if you can find some correlation?
Not sure what you mean by correlation. I can tell you this happens intermittently, not all the time. So getting a trace would require us to place an open ended trace on the server and hoping this happens during that time frame.
David Benoit (6/19/2013)
Can you give any details into what the job is doing? Is it possible that the database is owned by team member that is a sysadmin and when the user is executing the job / job step that it is switching context. Far stretch, I know. Grasping at ideas....
1) See above.
2) Database ownership? You mean as in who owns MSDB? Well, now that I look at it, the SA account does own MSDB. I wonder if that's the issue.
Does this make sense to everyone? MSDB being owned by SA would force other accounts to use its credentials when running jobs?