Limitation Considerations for MS SQL job schedule

recently encountered a special case of MS SQL job Schedule Limited, there is a job, the user requested to execute the time is: 9:30,14:30,16:30, 19:00, so I set two schedule, one every 5 hours to execute, The time range is 9:30~ 14:30.Another job schedule is executed every 150 minutes, time range 16:30 ~ 19:00, after the result is set, the user feedback job is not executed at 19:00, but 18:10 executes, I go to check, use SSMs Client (2014) to open check, After discovering the settings every 150 minutes, when you click Save, thisThe value is automatically changed to 100. Yes, you're right, you can test yourself if you don't believe it.

Log on to the server to check (the database is Microsoft SQL Server R2 (SP3)-10.50.6000.34 (X64)), click Edit Schedule, found the following error. And can not be edited at all, only delete schedule, And then add a new one,

Value of ' valid ' is not a for ' value '. ' Value ' should be between ' Minimum ' and ' Maximum '.

Parameter Name:value (System.Windows.Forms)

Results found in SQL Server R2 under the schedule, you will find that the SSMS 2008 client is edited in minutes, this value cannot exceed 60, and SQL Server 2014 under this value cannot exceed 100

This is a very wonderful limit, I do not know what is the purpose of such a restriction? I believe many people, like me, have not noticed that there are some limitations to the schedule of SQL Server jobs. I hereby record this case!

Limitation Considerations for MS SQL job schedule