Before upgrading to .NET Data Provider for Teradata version 14.10, please note that application changes may be required due to new feature content provided in this release.
Beginning in .NET Data Provider for 14.10, the logon process has been updated to execute in a Unicode session character set. In earlier releases, the logon was executed in the users session character set. Execution of the logon process in a Unicode session accommodates an expanded set of characters, introduced in Teradata Database release 14.10.
This change may affect characters that are not 100% compatible with the corresponding code page in Windows. For example, the KANJISJIS_0S session character set is not 100% compatible with the Windows code page 932 (Windows code page that supports Japanese Shift-JIS).
A user name (or other logon object name) created in one of these non-compatible session character sets may not be created the same depending upon the .NET Data Provider version. The Teradata Database may translate the character differently, since the .NET Data Provider for 14.10 executes all logons and the TdConnection.ChangeDatabase command in a Unicode session character set. Prior to the .NET Data Provider for 14.10, any characters created from these non-compatible session character sets could produce a different character value in the Teradata Database.
A possible workaround would be to provide the expected character in the previous logon that may be found by selecting the hexadecimal value of the translated character from the Teradata DBC.DatabasesV view. For an example of providing a Unicode code point within a logon string, see Connection Process Executed in Unicode.
What's New in the .NET Data Provider for Teradata 14.10