When you configure the general setup of a Teradata system, the Character Set settings allow you to define the charset that the system uses to communicate with Teradata Viewpoint. The character set definitions are optional. If you do not define them, Teradata Viewpoint uses the Teradata system settings.
|Character Set Fields||Character Set Definition Suggestions|
|Session||The UTF8 session character set is strongly recommended for the Teradata Viewpoint session to provide end-to-end fidelity of character data by avoiding conversion between character sets.|
|Monitor||The UNICODE session character set is supported by Teradata Database 14.10 and later.|
|JDBC Flag||The JDBC Flag setting is a legacy-support feature to assist the transition away from the unsupported use of Teradata Database to store non-Latin characters in a Latin column, and the unsupported access of non-ASCII in an ASCII session character set. The JDBC Flag option specifies the CLIENT_CHARSET connection parameter, which can be used to override the Teradata JDBC Driver fixed-mapping of the Teradata session character set to the Java character set. The valid values are the actual Java character set names. Here are two examples of valid JDBC Flag settings:
The default Teradata system settings are listed below.
|Teradata Database||Language Support Mode||Data Dictionary Charset||Teradata Viewpoint Session Charset||Teradata Viewpoint Monitor Charset||Limitations|
|14.10 and later||Standard||UNICODE||UTF8||UTF8|
|14.10 and later||Japanese||UNICODE||UTF8||UTF8|