sql server job is not running based on schedule

Shi, Hui 1 Reputation point
2021-02-04T06:48:06.343+00:00

hi all:
I have a very interesting case .
There is a Database Full backup job and it had a schedule to run on a daily basis at 12am. I've changed it to run on a weekly basis but after a few days, I was surprised to find that this job was still running on a day basis instead of weekly basis...
What's more , job history showed this job was invoked by sql service account directly instead of a schedule ID and job running time was not even 12am.. it was not a fixed time .

I just could not figure it out why this job is not running based on schedule I've modified.

Does anyone have this weird thing before?

Cheers

Hui

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories

0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Cris Zhan-MSFT 6,676 Reputation points
    2021-02-05T06:47:56.243+00:00

    Hi,

    If you restart the SQL server agent service after modifying the schedule, but this is still the case, please try to delete and recreate this job.

    Was this answer helpful?

    1 person found this answer helpful.
  2. Derek Wallace 0 Reputation points
    2026-08-04T20:34:01.3066667+00:00

    Hi all, I hit this issue this evening after failing over and back between High Availability Secondary and Primary nodes. I scripted the jobs to drop and create. Issue is resolved. I also ran an integrity check on the msdb database and it had zero errors. Hope this helps someone at some point in time. Derek

    Was this answer helpful?

    0 comments
  3. Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator
    2021-02-06T10:34:06.007+00:00

    I can think of two ways to track this down:

    1. Add a trigger on a suitable table in msdb to log information. Of course, since this a production environment, this is not without risks. If you mess up the trigger, you may wreak havoc with Agent on the instance.
    2. A trace where you include the event SP:Starting and filter for sp_start_job. Alternatively an X-event session with the module_start event.

    But since you said this was with Ola's maintenance solution, I have a theory. I seem to recall that he has a feature that permits you do things in parallel, and he implements this by having multiple jobs. Does this ring a bell?

    Was this answer helpful?

    0 comments
  4. Shi, Hui 1 Reputation point
    2021-02-06T00:10:21.907+00:00

    is there any way to find out which process called a sql job? this may help find out the hidden process. According to job history, execution start time ometimes is from minutes and even seconds... No normal sql schedule will be scheduled like this.

    Was this answer helpful?

    0 comments
  5. Erland Sommarskog 136.2K Reputation points MVP Volunteer Moderator
    2021-02-04T22:45:43.6+00:00

    Another job that starts this job with sp_start_job?

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.