Timeline for Can a MSSQL job change its own active schedule?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31, 2019 at 16:11 | vote | accept | WillG | ||
| May 30, 2019 at 16:26 | comment | added | Paul Holmes | Another idea: Job is executed once. Loop with a WAITFOR DELAY. When the condition is satisfied, exit. Optionally, also exit if it's no longer Sunday. Maybe THROW an error, if you want job history to highlight you didn't get the expected condition in your time window). No schedule modding, no history cleaning. | |
| May 30, 2019 at 6:33 | answer | added | Dat Nguyen | timeline score: 0 | |
| May 29, 2019 at 22:03 | history | edited | WillG | CC BY-SA 4.0 | added 11 characters in body |
| May 29, 2019 at 21:35 | comment | added | WillG | @AaronBertrand thanks for the link, I'll be looking at that later. | |
| May 29, 2019 at 19:58 | answer | added | James | timeline score: 1 | |
| May 29, 2019 at 19:37 | comment | added | Aaron Bertrand | Job history for successful runs is easy to keep clean (or only keeping the runs that made it to a certain step, for example). I wrote a starter piece here. I'm also thinking that if the record doesn't appear until Friday or Saturday that your OCD is on the wrong end of the deal. | |
| May 29, 2019 at 19:36 | comment | added | WillG | @AaronBertrand It's more my OCD, I don't want the job history spammed with all the unneeded runs. | |
| May 29, 2019 at 19:35 | answer | added | Laughing Vergil | timeline score: 0 | |
| May 29, 2019 at 19:24 | comment | added | Aaron Bertrand | How do you plan to change it back next Sunday? Wouldn't it be cleaner to just let it run every 10 minutes and quit with success if the record is there and it's not Sunday yet? | |
| May 29, 2019 at 18:29 | history | asked | WillG | CC BY-SA 4.0 |