Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| 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. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Troubleshooting: Slow execution of queries
Slow query execution time is usually related to hardware and network limitations, or report design. After eliminating hardware or network limitations as a source of the slow response time, you can apply the following suggested tips to your report designs to speed execution:
- Limit the number of records kept in a database table, such as avoid saving several years of incident records in a single database table. The more records that are kept in a file, the larger the index is. The larger the index is, the slower queries run.
- Limit sorting layers. If the raw SQL contains more than two ORDER BY statements, the processing time increases. Each ORDER BY statement significantly increases execution time.
- Use joins instead of subreports. Although subreports are universal and allow greater portability over different servers, they execute SQL queries against the database one time for every record. For example, a report with 100 records with a subreport in the Details section executes 101 SQL statements. A joined report of equivalent size executes only once.
- Use indexes where possible. Typically, the Unique key of any table is already indexed; however, in a join, placing a key on the field used to join the two tables dramatically increases the speed to execute. Add indexes only with the guidance of your Service Manager administrator. Adding too many indexes to a Service Manager table can affect performance.
Related topics
Key type definitions
Troubleshooting: Database debug
Tuning: Designing keys for queries
Tuning: Key selection algorithms
Tuning: Number of fields in files
