I've got this job that needs to be executed in prod during downtime at exactly 9pm EST, starting with a backup. But the database that ill be setting up this job for is large and may take up to 45mins to complete the backup process and kick off execution of the rest of the job, which i need to make sure starts at exactly 9pm EST. So I've got my job steps listed with backup to start at 8:15pm so that it finishes at 9 and the required changes/scripts are made/run
My question today is... what if this backup that I expect to take 45mins ends up taking 35 and the changes are made to prod before the required time?
Is there anyway that i can have different schedules for different steps within one job cos i have not been able to figure it out, not even with SSIS, or i should simply just separate the jobs and allow a +/- 15mins gap between them.
Just my thoughts, i don't even know if this makes any sense
What I am hearing you have:
Step 1 @ 20:15: take backup assuming it takes 45 minutes
Step 2: run important stuff that you want to run at 21:00
What you may want:
New Backup Job starts at 20:15:
Step 1: take backup
Existing Job, modified, starts at 21:00:
Step 1: run important stuff that you want to run at 21:00
PS: the big question I have is, what if the backup takes longer than 45 minutes? do you still want your changes to start at 21:00 or wait for the backup to complete?
There are no special teachers of virtue, because virtue is taught by the whole community.