17.20 - Client Character Set Compatibility with Server Character Sets - Advanced SQL Engine - Teradata Database

Teradata Vantageā„¢ - Advanced SQL Engine International Character Set Support

Advanced SQL Engine
Teradata Database
Release Number
June 2022
Last Update
Content Type
User Guide
Publication ID
English (United States)

To be usable, a client character set must 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.
    The current system default is defined in the DBSControl DefaultCharacterSet field.

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:

If the default server character set is... The client character set can be...
  • EBCDIC037_0E
  • EBCDIC277_0E
  • EBCDIC273_0E
  • LATIN1_0A
  • LATIN9_0A
  • LATIN1252_0A
  • A simple site-defined ASCII-based character set
Do not use client character sets other than those listed to insert data into a LATIN column, even if the character set appears to be represented in LATIN (for example, Turkish). The system may incorrectly translate such characters when converting them to UNICODE.
UNICODE Any valid single- or multibyte client character set.
KANJISJIS KANJISJIS supports mixed single and multibyte characters and its form-of-use is identical with that of its client character set analog
GRAPHIC Multibyte characters from the defined Graphic repertoire of the following character sets:
  • KanjiEBCDIC
  • KanjiSJIS_0S
  • KanjiEUC_0U