Changing Character Set Defaults - Teradata Database - Teradata Vantage NewSQL Engine

Teradata Vantage™ - Database Administration

Product
Teradata Database
Teradata Vantage NewSQL Engine
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2019-05-03
dita:mapPath
tgx1512080410608.ditamap
dita:ditavalPath
TD_DBS_16_20_Update1.ditaval
dita:id
ujp1472240543947
Product Category
Software
Teradata Vantage

You can change the default client character set and the default server character set at the user level, and the user can choose alternatives during a session.

Default Client Character Set

If you do not define a client character set as the default for a client in the DBC.Hosts table, the automatic default is the character set native to that client.

During a session, you can find out which client character set is in effect with the SQL HELP SESSION statement and can specify a different (but active) client character set in various ways, depending on the particular client software. For example, with the BTEQ client software, you can use the SESSION CHARSET command:

.SET SESSION CHARSET ASCII

For details on when the SESSION CHARSET command can be used, see Basic Teradata® Query Reference, B035-2414.

Default Server Character Set

To specify the character set for a user, issue a CREATE USER or MODIFY USER request with the DEFAULT CHARACTER SET clause. If you do not specify this clause when you create or modify a user, the setting of the Default Character Set field in the DBS Control utility determines the default character set.

The default value for the Default Character Set field is 0 (Unicode) for Japanese Language Support mode and 1 (Latin) for Standard Language Support mode.

If you change the character set for user DBC, user-defined functions may not work without being recompiled. You must also:
  • Rerun DIPUDT and DIPDEM
  • Recompile any site-defined DBC functions that use SQL_TEXT