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 |
|
Splitting SQL tables
The Service Manager server reads the row size limitation and column number limitation from file "sqldbinfo" and uses the information when making a decision about whether to split SQL tables or not. This applies to all supported database servers.
Note By default, for SQL Server, all fields are put into M1 and will never be put into M2 or other “M” tables.
Caution Modifications to the "sqldbinfo" table require a restart of the Service Manager server.
Constraints when disabling the row size limitation on SQL Server
If you want to disable the row size limitation on SQL Server, you need to consider the following constraints:
- The length of individual columns must still fall within the limit of 8,060 bytes for varchar, nvarchar, varbinary, sql_variant, and CLR user-defined type columns. Only their combined lengths can exceed the 8,060-byte row limit of a table.
- The sum of other data type columns, including char and nchar data, must fall within the 8,060-byte row limit. Large object data is also exempt from the 8,060-byte row limit.
- After removing the row size limitation, if a file does have an M2 table, before you manually move all of the fields in M2 into M1, newly added fields will still be put into M2.
- If you want to disable table splitting, you need to manually set the row size limitation in the “sqldbinfo" table to a very large number, which is supported by SQLSERVER 2008 and later with ROW_OVERFLOW_DATA. The Row-Overflow feature is great for allowing occasionally rows longer than 8,060 bytes, but it is not well suited for the majority of rows being over-sized, which can lead to a drop in query performance.
Related topics
Automatic update of database dictionary records
Database dictionary
Database dictionary records
SQL data type for localizable fields
Add a field to an existing database dictionary record
Create an active database dictionary record
Create an inactive database dictionary record
Update the data type of a database dictionary field
