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.
|A single word||
||Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".|
You can specify that the search results contain a specific phrase.
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.
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||
|A combination of search types||
- Server performance tuning
Defining record identifiers in batches using the numbers file
Administrators can define record identifiers and allocate those identifiers in batches from the
numbers file for new interactions, incidents, and changes. By allocating record IDs in batches in advance, administrators can reduce traffic between the Service Manager server and the RDBMS, which improves overall system performance.
- Currently the
countersfile is used by administrators to define the table and field where a new record number is going to be stored. However, the
numbersfile is still available for those who previously chose to define record numbers using the
numbersfile and are upgrading. This file has been enhanced to work more like the
countersfile. For more information on the
countersfile, see the related topics.
- In the case of 32-bit systems, the value range for long signed integer is between -2,147,483,648 and 2,147,483,647. Make sure the numbers generated via
counterstable are not out of the range. Otherwise, wrong querying result and unexpected error might occur.
When using the
numbers file, administrators define the following:
- Batch size.
- Starting number.
- Identifying prefix for each module. For example, IM for Incident Management records.
- Whether numbers are going to increment or decrement.
- The table and field where the new numbers are to be stored.
When you define a batch size, Service Manager retrieves that number of ID keys from the RDBMS and stores the keys in shared memory for later use. Each time someone creates a new record, the system assigns it an ID key from shared memory until there are no more IDs available. Once the system exhausts its supply of IDs, it requests the next batch of IDs from the RDBMS.
We recommend you set the batch file size to the number of new records you expect users to create in an hour, divided by the number of servers in the implementation. For example, if you expect to generate 200 incident records an hour and have only one server in your implementation, then set the Batch Size value to 200. If your system consists of multiple servers, such as in a horizontal scaling implementation, then divide the total records per hour by the number of servers. For example, a horizontal scaling implementation with four servers only needs a batch size of 50 for each server to equal 200 incidents per hour.
In a horizontally scaled system, each server requests its own batch of ID keys. Since new records may be created from processes running on different servers in a horizontal scaling implementation, the ID numbers of new records may not be in sequential order. For example, process A on server 1 has reserved ID keys 1-100 and process B on server 2 has reserved ID keys 101-200. The first record a user creates on process A will have ID 1, but if the very next record created comes from process B, then the ID will be 101, not 2.
If you do not specify a batch size value, Service Manager uses the default batch size of 1 and fetches a new ID from the RDBMS for each new record you create.
Example data from a numbers file
TABLE_NAME COLUMN_NAME CURRENT_VALUE BATCH_SIZE irqueue counter 0 100 schedule schedule.id 2587564 1000 scirexpert record.id 5198034 5000