Specifying multiple schedules for one resource limits group
Specify resource limits during different time periods using multiple schedules for one resource limits groups.
When a user accesses a data source the resource limits groups to which the user has been assigned are identified. The schedules of the identified groups are verified to determine which resource limits are currently in effect. Because users can be assigned to multiple resource limits groups, each with multiple schedules, there can easily be overlapping spans of time when technically multiple sets of resource limits could be in effect.
In the cases of overlapping schedules, a unique schedule number is used to determine which schedule is in effect. The schedule with the lowest number takes precedence.
| Schedule # | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| From Day | Wednesday | Monday | Monday | Sunday |
| To Day | Wednesday | Friday | Friday | Saturday |
| From Time | 10:30 | 9:00 | 17:00 | 00:00 |
| To Time | 11:30 | 17:00 | 9:00 | 24:00 |
You will notice that schedule #1 is embedded in schedule #2 and schedules #1, #2, and #3 are embedded in schedule #4. If a user accessed this data source on Wednesday at 11:00, schedules #1, #2, and #4 could be in effect. The schedule with the lowest number is used.
When you create your resource limits group schedules, it is recommended that you stagger your numbering so additional schedules can be inserted where appropriate or deleted without impact. Keep in mind that schedules do not have to be numbered sequentially but once a schedule is assigned a number it cannot be changed.
All time and day ranges of the schedules are inclusive. That means if the From time is 08:00, the schedule is in effect exactly at 08:00. If the To time is 17:00 the schedule is in effect until 16:59:59. The from and to times can wrap around midnight, and the from and to days can wrap around weekends.
When users are accessing data sources in different time zones, the clock used to determine time resides on the data source being accessed. For example, a user in New York is accessing a data source in California and it is 9:00 AM Monday in New York. Based on the example schedules, schedule 3 is in effect because according to the data source it is 6:00 California time.