More aimed at the "constant" jobs such as backup copy jobs, but it would occasionally be very
useful to be able to configure a job to pause or disable after the current cycle, without having to edit the config of that job.
In this particular case, I'm having an issue with the merge process taking longer than expected and have been issued with a hotfix but the sync cycle of the copy job started itself again for some reason overnight so I'm going to have to wait for that to complete, then for the (very slow) merge process to also complete before I can safely stop the services and apply the hotfix.
I know you can edit the job & create a maintenance time window within its schedul but I really dislike the impact this has on the scheduling/cycle of copy jobs as it always seems to throw timings out (because you have to stop & restart the job for the changes to take effect, and then you have to edit the job again
after you've completed your maintenance, which resets the clock & impacts the timings once again).
Actually, what would REALLY be quite useful is something along the lines of a "Global Maintenance Window" that is somehow centrally managed and, most importantly, which ALL JOBS must watch for and honour regardless of their own time window settings, stopping gracefully when told to do so.
Good idea or crazy/lazy/greedy?