July 22, 2013 at 4:06 am
Hi,
I have a job scheduled to run every 2 hours during the week.
The job started to run at 1:15 PM on Friday afternoon as scheduled (confirmed from the steps log and also since the consequent scheduled jobs failed due to "Failed to start job -job already in running state" type of error message)
During the weekend, as part of maintenance activity any unprocessed records are moved to a history table and have been moved. However the job activity monitor doesn't even list that the job executed. The last execution it shows is of 11:15 the same morning as per schedule.
The file that was supposed to be created at the end of the job is also not created, however the records in the table mean that the job was executed.
Cant seem to trace the job history.
Help!!
July 22, 2013 at 2:26 pm
1) You may have to delete the job and re-create it with small steps and verify its running fine.
2) Check if your SQL Agent is properly configured
3) Check for SPs
July 22, 2013 at 2:37 pm
I'd guess that the history settings are default, which is 1000 TOTAL rows of history and up to 100 rows per job. With those settings its REALLY easy to lose history.. I set the numbers VERY high, like 999,999 total rows and up to 5,000 rows per job.. YYMV.
CEWII
July 23, 2013 at 6:14 am
I had thought that. However, I fail to understand that with so many jobs in there, why would it delete the history of only 1 instance of this 1 job.
July 23, 2013 at 7:43 am
If you had 10 other jobs that run often they could generate up to 100 history records each they can easily displace the history records for jobs that run less often.
Remember with the default settings there is only 1000 history records TOTAL for all jobs and jobs are may generate more than one history record in a run. So if you have a job or two that runs REALLY often it can play havoc with job history. Just run those numbers up and that should help..
CEWII
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply