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.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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
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.
Another job that starts this job with sp_start_job?
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.
I can think of two ways to track this down:
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?