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. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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.


migration rejected from Sep 16 '14 at 16:37

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as off-topic by Max Vernon, RolandoMySQLDBA, Mark Storey-Smith, Paul White, Shawn Melton Sep 16 '14 at 16:37

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Too localized - this could be because your code has a typo, basic error, or is not relevant to most of our audience. Consider revising your question so that it appeals to a broader audience. As it stands, the question is unlikely to help other users (regarding typo questions, see this meta question for background)." – Max Vernon, RolandoMySQLDBA, Mark Storey-Smith, Paul White, Shawn Melton
If this question can be reworded to fit the rules in the help center, please edit the question.

can you check enabled Property in schedules ? – Feb 5 '14 at 6:15
Ya; i have checked that already and that was enabled. – Ravi Feb 5 '14 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 '14 at 13:53
So, what is different about this job? – Aaron Bertrand Feb 5 '14 at 14:00
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. – Shane Estelle Feb 5 '14 at 16:55