Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Service Management2017.11

Administer > Scheduled maintenance > Scheduled Maintenance overhead

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 ITSMA Service Management 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.

Send Help Center feedback