Scheduled Maintenance overhead

Scheduled Maintenance relies on the problem background scheduler to call into the Scheduled Maintenance code at regularly scheduled intervals. If the problem scheduler is not running, no Scheduled Maintenance tasks run. When a Scheduled Maintenance task runs, it increases the load on the problem scheduler by a marginal amount.

Scheduled Maintenance does not put a large load on your system unless you are using the Scheduled Maintenance system to generate extraordinarily large numbers of incident records, change requests, or Request Fulfillment requests. If Scheduled Maintenance creates twenty tasks a day, the impact is approximately identical to one user opening twenty tasks a day.

If a Scheduled Maintenance task creates 20,000 Incident records at 2:00 AM, the task would slow the Service Manager system down somewhat. Scheduled Maintenance creates all 20,000 records consecutively, as though one user were opening 20,000 incident records consecutively. The increased load may be noticeable, but it will not be crippling.

Load balancing

You should not notice any change in your system load when you use Scheduled Maintenance. However, if you have an unusually large number of tasks opening every day, such as 1000 each day, or over 100 in a 10-minute period, consider creating a private scheduler that runs only Scheduled Maintenance tasks. When you create and run this scheduler, change the class on the Scheduled Maintenance Hook record to match your new scheduler. You can also change the repeat interval on the inhook schedule record.

Access the Scheduled Maintenance Hook record

To access the Scheduled Maintenance Hook record:

1. Click Tailoring > Database Manager.
2. Type schedule.looksee in the Form field.
3. Type schedule in the Table field.
4. Click the large Search icon.
5. Click Search.
6. Click the Scheduled Maintenance Hook record to view it in the Schedule File form.

Note: The minimum effective repeat interval is one minute. This interval causes the server to check for tasks every minute. With adjustment, you can reduce this to about 10 seconds. You cannot reduce the interval to less than 10 seconds because of the internal structure of the Service Manager scheduling system.