A translation library is a dynamic linked library that contains functions for translating all the data flowing between the Teradata server and the driver. Translation DLLs are used if local character sets are not supported by the ODBC Driver or Teradata.
After a translation DLL has been specified, the driver loads it and calls it to translate all data flowing between the application and data source.
- All SQL statements
- Character parameters being sent to the data source
- All character result set data
- Character meta data such as table and column names
- Error messages retrieved from the data source
Connection data is not translated, because the translation DLL is not loaded until after the application has connected to the data source.
Refer to the ODBC Programmer's Reference for information on how to write a translation DLL.
For UNIX OS clients, use the CharacterSet keyword instead.
To define the translation DLL name and option, use the Teradata ODBC Driver Advanced Options dialog box. The example in the figure that follows shows that user uses Translation.dll as the translator.
For UNIX OS clients, use CharacterSet TransitionDLL, and TranslationOption instead. The Translation DLL path cannot be more than 255 characters. Translation Option is used by translation DLL and optional. The driver will convert it to a 32-bit integer and pass it to the translation DLL. Translation DLL can be used for a supported session character set but it is strongly discouraged.
For an example of translation DLL, refer to sample translator that comes with the Driver Manager.