Default Case Specificity of Character Columns | Teradata Vantage - Default Case Specificity of Character Columns - Teradata Vantage - Analytics Database

SQL Data Types and Literals

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
ft:locale
en-US
ft:lastEdition
2025-11-06
dita:mapPath
uds1628112204571.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
exs1472253032394
lifecycle
latest
Product Category
Teradata Vantageā„¢

Default case specificity varies with mode.

Case specificity does not apply to CLOB types.

ANSI Mode

CHARACTER and VARCHAR data columns defined in ANSI mode are defined as CASESPECIFIC by default. This means that the values 'aa' and 'AA' are not treated as equals.

An option of NOT CASESPECIFIC is implemented to allow columns to be not case specific. NOT CASESPECIFIC is a Teradata extension to the ANSI standard.

Teradata Mode

CHARACTER and VARCHAR data columns defined in Teradata mode (with the exception of character data defined as CHAR or VARCHAR CHARACTER SET GRAPHIC) are defined as NOT CASESPECIFIC by default.

Because Latin characters have canonical representation in all Vantage character sets, the effect of the UPPERCASE function is the same for each character set (with the exception of KANJI1, where multibyte characters are not converted to uppercase).

The CASESPECIFIC and UPPERCASE phrases are described in detail in: