Client Character Set Compatibility with Server Character Sets - Teradata Vantage

Teradata® VantageCloud Lake
Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
ft:locale
en-US
ft:lastEdition
2024-12-11
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

To be usable, a client character set must be compatible with the applicable default server character set.

The default server character set is determined in the following hierarchical order. If a default is not defined, the system defers to the next lower item on the list:

  1. Table column default character set
  2. User default character set
  3. System (global) default character set.

For more information about defining the default server character set, see Specifying the Default Server Character Set.

The following table lists client-server character set compatibilities:

Default Server Character Set Compatible Client Character Sets
LATIN
  • ASCII
  • EBCDIC
UTF8 and UTF16 can be used, but not all the characters available in these session character sets can exist in LATIN.
UNICODE Any valid single- or multibyte client character set.
KANJISJIS
  • UTF8
  • UTF16
Not all the characters available in these session character sets can exist in KANJISJIS. ASCII and EBCDIC client character sets can be used, but the purpose of KANJISJIS is to extend LATIN to include Japanese characters, and there are no Japanese characters in ASCII or EBCDIC.
GRAPHIC Multibyte characters from the defined Graphic repertoire can only be used with UTF16. GRAPHIC is specifically designed to reject a certain set of UTF 16 characters.