If you are installing the Unicode version of Perceptive Content then you must manually specify the appropriate default collation for your database. Be mindful of the tempdb database collation when selecting the default collation as incompatibilities between collations, in some cases, can cause unexpected errors and require the use of expression-level collations.
For Unicode installations, we use the nvarchar data type for character data. The collation you choose further defines the character encoding to either UTF-16 or UCS-2 encoding. The collation also determines the rules applied to character data with regard to evaluating characters within SQL expressions such as string compares for data access and filtering and sorting of results.
For Unicode installations, we recommend that you select a collation that best fits the primary language you are using to drive the business. If you are primarily using English to conduct day-to-day operations then you may want to use the Windows collation Latin1_General_100_CI_AS (code page 1252) for the default database collation.
- We recommend you avoid using Binary collations (*_BIN*) because they do not support CI (case insensitive searching) and could lead to undesirable results within Perceptive Content.
- Perceptive Content is designed to work with case-insensitive collations. Choose a collation that includes the _CI option.