Has anybody else seen the limit Management Studio's interface puts on the scheduling of jobs? Specifically, if the units is "minutes", the frequency can't be more than 60 (and similarly, the limit for "hours" is 24).
Thanks!
-dave
Yes, we've seen that. Is there a question?|||Heh.. sorry. I guess the question/assumption is... that's a known bug and will be fixed at some point (?).
Thanks!
|||A bug would mean that it isn't working as designed. This isn't a bug. You can only configure 60 when you select minutes for a value, because there are only 60 minutes in an hour. You can only configure 24 for hours, because there are only 24 hours in a day. I'm not sure what you're trying to do.|||Michael,
I can easily see times to have a JOB execute every 90 minutes, for example. The Current scheduling GUI doens't allow that without using 'creative' options.
More flexibility with the scheduling GUI would be an excellent move!
|||Arnie beat me to it, but... yes, every 90 minutes is a good example.
FWIW, I ran into this while trying to implement Quest LiteSpeed's log shipping solution. Their l/s wizard adds a job with twice the l/s interval, which I'd set to 60 minutes. (Oddly enough, their own Enterprise Console front end won't let you put in more than 100 minutes... very strange). Trying to edit that job's schedule with Management Studio gives a popup error box and does not allow entry to the schedule (in effect: "the schedule has an error, but we're not letting you in to fix it").
Finally, this is yet ANOTHER instance of regression from 2000 to 2005, in that Enterprise Manager has no such limit.
|||MSDN Product Feedback Center. Post a suggestion. Then get a bunch of people to vote on including it. Yes, you do have the ability to directly influence feature requests.