17.20 - Customizing the Defined Collations - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database International Character Set Support - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-01-27
dita:mapPath
aju1628095815656.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
hqj1472245413611

A defined collation is active for all server character sets, but they are not applied equally.

You can change the MULTINATIONAL collation for all 256 characters in LATIN, and this definition holds true for those characters whether they occur in GRAPHIC, KANJISJIS, or UNICODE. Note that KANJISJIS and UNICODE have many more characters than LATIN and that the “extra” characters continue to follow the default multinational collation rules.

The collation is two level, which, in the following case specific example, allows you to specify a collation that always produces the following ordering:

  1. aa
  2. Aa
  3. ab
  4. Ab

A single-level, case blind collation might give that answer sometimes, but could theoretically also produce several other orderings, such as the following, on consecutive queries:

  1. Aa
  2. aa
  3. ab
  4. Ab