Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I have scheduled a SQL job to run daily at 3am in the morning which creates a batch.

It has not run today and i am also not able to fathom what's the reason behind its failure. There is no entry in its log file that why it has failed. In fact from the history it seems like it has not even tried to execute itself.

Rest of the jobs scheduled at 3 am have run successfully.

The account from which this job is run is also the service account so that also eliminates the case of the person being removed from the AD which i have come across on some of the blogs that it could be one of the reasons in such scenarios.

share|improve this question

migrated from stackoverflow.com Feb 5 at 12:21

This question came from our site for professional and enthusiast programmers.

    
can you check enabled Property in schedules ? –  ram.bi Feb 5 at 6:15
    
Ya; i have checked that already and that was enabled. –  Ravi Feb 5 at 7:04
    
If the job is not running, this is usually because a schedule is misconfigured. Have you validated that the "Next Run" datetime is at 3 AM? –  Mike Fal Feb 5 at 13:53
    
So, what is different about this job? –  Aaron Bertrand Feb 5 at 14:00
    
Did you look in the SQL Agent's log? –  Peet Brits Mar 19 at 8:32

1 Answer 1

This might be a silly question, but are you out of disk space where the MSDB system database is located? This can cause job history to not be logged among other things.

It's the only thing I can think of other than miss-configuration of the job itself.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.