0

On SQL Server I used maintenance plan wizard to create three jobs:

Job Schedule
Job 1 Every 3 week on Sunday
Job 2 Every 3 week on Sunday
Job 3 Every 3 week on Sunday

I want the three jobs to run like so:

Date Job
Sun 2022-01-09 Job 1
Sun 2022-01-16 Job 2
Sun 2022-01-23 Job 3
Sun 2022-01-30 Job 1
Sun 2022-02-06 Job 2
Sun 2022-02-13 Job 3

And so on. But Job Activity Monitor shows the "Next Run" date for all three jobs as Sun 2022-01-09. I tried to change the "Start date" of schedules to three consecutive Sundays in the past e.g. Sun 2021-12-19, Sun 2021-12-26 and Sun 2022-01-02 but no joy. Please advise.

Improve this question
3
  • Did you try using Frequency tab and define job1 to run every 3 weeks on Sunday starting from 9th January? Second job again with same recurrence starting from 16th Jan and job3 with same recurrence starting from 23rd January?
    – Learning_DBAdmin
    Jan 4, 2022 at 10:51
  • That works, thanks. Any idea why it cannot use past dates to determine the sequence?
    – Salman A
    Jan 4, 2022 at 10:59
  • You can use Past dates also by getting into "Duration" tab at start date column
    – Learning_DBAdmin
    Jan 4, 2022 at 11:00

1 Answer 1

Reset to default
4

This can be achieved using Frequency part of Scheduler.

You may create three jobs schedule, For Job1 as below:

enter image description here

Same thing will be repeated for Job2 and Job3 however you need to change start date to 16th and 23rd January in this part:

enter image description here

You may also use Past dated by changing date from the above calendar. After the job has executed, SQL Server will calculate a Next Execution date and time. So if you simply revert the system clock then it will be waiting for the next scheduled execution, it won't work that way. Better to schedule from current date and onwards.

Hope this helps.

Improve this answer
2
  • Past dates do not seem to work. E.g. When I use 2021-12-19, 2021-12-26 and 2022-01-02 for Job 1, 2 and 3 they all have next date = Sun 2022-01-09.
    – Salman A
    Jan 4, 2022 at 11:08
  • 1
    After the job has executed, SQL Server will calculate a Next Execution date and time. So if you simply revert the system clock then it will be waiting for the next scheduled execution, it won't work that way. Better to schedule from current date and onwards.
    – Learning_DBAdmin
    Jan 4, 2022 at 11:15

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.