SICSR-16109

[SICSR-16109] Incorrect handling of (VAR)CHAR table columns on Unicode-enabled databases
Product Line:	P&C
Component/s:	Database Setup
Affects Version/s:	SICS 4.8
Fix Version/s:	SICS 20.1
Customer:	DXC

Problem:
When unicodeMode=true (which is only made available by SICS for SQL Server databases), a performance hit may occur when an index column is CHAR/VARCHAR and there is a literal-based predicate on that column in a query (parameterized SQL, or static/literal SQL). As the literal value will be Unicode, it is not directly comparable with the non-Unicode index column.

Solution:
Make sure literal values used in query predicates are conveyed as Unicode if the column type is N(VAR)CHAR, and as non-Unicode (ASCII, really) if the column type is (VAR)CHAR.

For existing Indexes requiring Unicode Mode to be set (Unicode DB's only) then a Database Patch will drop and recreate the indexes.

Workaround:
None

Root Cause:

Extent of Impact:

Impact on Existing Data

Recovery Method for Existing Data Affected