OpenEdge Data Management: DataServer for Microsoft SQL Server

Initial Programming Considerations
2–8
Code page, collation, and case conflicts
How you specify code page, case sensitivity, and shadow column usage can lead to conflict
between the attributes. It is best to establish the settings on these attributes prior to schema
creation, and allow the schema pull to manage the integration into the schema image. Table 2–3
describes the behavior of the combinations.
Table 2–3: Case sensitivity interactions
Code Page 1
Shadow
Columns
Case Sensitive
Field Attribute Result
CS Yes Off Shadow column
provides case
insensitivity
CS No Off UPPER() function
provides case
insensitivity 2
CS Yes On Code page provides
case sensitivity
CS No On Code page provides
case sensitivity
CI Yes Off 3
(Is case-insensitive)
CI No Off
(Is case-insensitive)
1. The MS SQL Server code page is either Case Sensitive (CS) or Case Insensitive (CI).
Shadow column
provides case
insensitivity 4
Code page provides
case insensitivity
CI Yes On Code page provides
case insensitivity 5
CI No On Code page provides
case insensitivity 6
2. Be aware that relying on the UPPER() function can have a negative performance impact.
3. This combination is not recommended. Don’t use shadow columns if the MS SQL Server code page can handle
case-insensitivity instead.
4. This combination is not recommended. Use a code page to support case insensitivity by identifying the code page as
case insensitive on a schema pull. Fields will be marked case insensitive on the pull.
5. Shadow columns are present, but play no role.
6. Case sensitivity cannot be supported by OpenEdge. The client will throw out any results not returned in case
insensitive order.