16.20 - Character Sets - Teradata Database - Teradata Vantage NewSQL Engine

Teradata Vantage™ SQL Fundamentals

Product
Teradata Database
Teradata Vantage NewSQL Engine
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2019-05-02
dita:mapPath
zce1519094756513.ditamap
dita:ditavalPath
TD_DBS_16_20_Update1.ditaval

When making a request to the database, an SQL statement can be represented using any client character set that is available on the client and enabled in the database, including user-defined character sets.

Character Data

The system converts the SQL into UNICODE, and then converts any character literals from UNICODE to the data type of any column into which they are inserted.

If you enter data by way of a USING clause, the system stores the data based on the session character set, either LATIN, UNICODE, or KANJI1. As with any character data, if inserted into a character column, the USING data is implicitly translated to the character set of the receiving column.

If you create a character column, for example in a CREATE TABLE statement, and no character set is explicitly designated for the column, the column is created using the default character set.

Setting the Default Server Character Set

You can set the default server character set for:
  • A user in a CREATE or MODIFY USER
  • Profile members in a CREATE or MODIFY PROFILE statement
Upon upgrade to Teradata Database 14.10 and above from a pre-14.10 release, the server default character set is initialized based on the language support mode; LATIN for standard mode or UNICODE for Japanese mode.

Related Topics

For more information about:
  • Available character sets and enabling character set options, see Teradata Vantage™ NewSQL Engine International Character Set Support, B035-1125.
  • Notation used for characters is described in the "Overview" topic in Notation Conventions.