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 Manager9.41

Administer > Database Administration > Case-sensitivity > MS SQL Server collation support

MS SQL Server collation support

HPE Service Manager supports two types of collations :

Those ending in some form of _BIN (binary)
Those ending in some form of _CI_AS (case-insensitive, accent sensitive)

_BIN is used for case-sensitive collation, meaning both, comparisons ( WHERE NAME="ADMINISTRATOR") and sorting ( ORDER BY NAME) are case-sensitive. Collations ending in _CS_AS claim to be case-sensitive, but that only applies to comparisons. For sorting, they use a "dictionary order," which is essentially case-insensitive.

_CI_AS is the supported case-insensitive collation. It uses case-insensitive comparisons ( WHERE NAME="AdMinIstrator") and case-insensitive sorting. Do not use _CI_AI since Service Manager has no concept of accent insensitivity.

The sort order becomes important in the case of a combined SQL/IR search. In that case, IR has to match its own results with the results returned by SQL, and for that it assumes binary or case-insensitive sorted order.

Note, that such queries might take place even if you don't know about them. For example in the Service Catalog, when ordering, a user enters an IR query, but the RAD appends a long non-IR query to it. This results in a mixed query.

The other aspect of the collation is the code page. The code page defines the code page of VARCHAR columns, NVARCHAR are always in UTF-16. "General" refers to the American default Windows code page, Win 1252.

Service Manager supports the following SQL Server code pages:

Code page	Description
874	MS cp874 Thai
932	MS cp932 Japanese
936	MS cp936 Simplified Chinese
949	MS cp949 Korean
950	MS cp950 Traditional Chinese
1250	MS cp1250 Central European
1251	MS cp1251 Russian, Bulgarian, Serbian
1252	MS cp1252 Latin/Western European
1253	MS cp1253 modern Greek
1254	MS cp1254 Turkish
1255	MS cp1255 Hebrew
1256	MS cp1256 Arabic
1257	MS cp1257 Estonian, Latvian, Lithuanian
1258	MS cp12578 Vietnamese

You can generate the list of all the code pages supported by Service Manager with the command, sm -reportlanguages. Only those code pages that start with "mswin" are used in the context of SQL Server.

If you are using an unsupported code page, you will see this warning in the log file: W SQL Server uses a code page <nnn> unsupported by HPE Service Manager which retrieved codepage <nnnn>.

Send Help Center feedback