17.20 - Session Character Sets and Translation DLLs - ODBC Driver for Teradata

ODBC Driver for Teradata® User Guide

Product
ODBC Driver for Teradata
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2022-06-21
dita:mapPath
uqj1639470627591.ditamap
dita:ditavalPath
nkw1500504256726.ditaval

The following table indicates SQLDriverToDataSource conversions. The subsequent table describes SQLDataSourceToDriver conversions. UTF8/UTF16 session character sets do not require translation DLLs.

Function of SQLDriverToDataSource
Convert Windows application code page to UTF16

The following table describes the functions of the SQLDataSourceToDriver.

Function of SQLDataSourceToDriver
Convert UTF16 to Windows application code page

User-defined session character sets can be used either with or without a translation DLL. If no translation DLL is specified, the driver's conversion is based on the current application code page. With Teradata-provided session character sets, no translation DLLs are needed as long as the session character set matches to the current application code page. For example, a Chinese session character set matches the Chinese Windows PC.

Teradata recommends that translation DLLs be copied to the same folder and location where the driver was installed.

KANJIEBCDIC5038_0I is supported on Windows systems when set up as a Japanese machine (CP932). Other configurations are not supported. This character set is used for communications to and from the database. The application must use the Windows CP932 session character set when communicating with ODBC Driver for Teradata. This behavior is identical to KANJIEUC_0U.