February 28, 2013 at 8:03 am
Hi Experts,
One of our maintenance job which was not supposed to run on weekdays executed 3 times today. Job history is showing its invoked by system account .
Is there any way we can figure out how the job started??
TIA
February 28, 2013 at 9:55 am
Please post the exact "invoked by" text from job history (with sensitive domain or user names masked of course).
Also, look for jobs that might kick off the job in question using msdb.dbo.sp_start_job.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 1, 2013 at 3:44 am
its sbcind\clusteradmin..
i tried sp_help_job but that didnt help.
March 1, 2013 at 8:00 am
OK, so not by a schedule which means something or someone besides the Agent scheduler kicked it off.
Anything from this after adding your job name?
SELECT j.name,
js.step_id,
js.step_name,
js.command
FROM msdb.dbo.sysjobs j
JOIN dbo.sysjobsteps js ON j.job_id = js.job_id
WHERE js.command LIKE '%sp_start_job%'
AND js.command LIKE '%your_job_name%';
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 1, 2013 at 8:52 am
Thanks for the reply.
Query didnt yield any result.
March 1, 2013 at 10:01 am
What times were they started? Does it look random or like a scheduled job? i.e. on the minute or hour every time? I might start asking around. Maybe someone logged in as a system account and kicked off the job a few times trying to fix something.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply