July 6, 2014 at 9:05 am
Hi,
We have hundreds of concurrent running jobs.
Each day some jobs (different ones) run in times when they are not scheduled.
Please see data from yesterday. I just can't explain the second row:
The job succeeded. The Job was invoked by Schedule 4107 (Schedule1). The last step to run was step 4. 20140705 190447
The job succeeded. The Job was invoked by User PROD\SQLAgentUser. The last step to run was step 4. 20140705 190021
The job succeeded. The Job was invoked by Schedule 4107 (Schedule1). The last step to run was step 4. 20140705 190001
The job succeeded. The Job was invoked by Schedule 4107 (Schedule1). The last step to run was step 4. 20140705 184938
The job succeeded. The Job was invoked by Schedule 4107 (Schedule1). The last step to run was step 4. 20140705 184518
The job succeeded. The Job was invoked by Schedule 4107 (Schedule1). The last step to run was step 4. 20140705 184010
There is no way that someone runs the jobs manually since when it happens there are 10-15 jobs that
suddenly start unexpected.
Thanks,
Tommy.
July 6, 2014 at 11:00 pm
We found the problem. It's a "fixer" job that start the other ones.
Sorry for wasting your time and for blaming SQL Server Agent 🙂
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply