In Teradata Database Release 14.10 object names have been lengthened from 30 bytes of a Latin or KANJISJIS character set to 128 Unicode characters. This capability supports a richer set of characters to compose object names. While using a session character set that may contain limitations due to the supported set of characters, Unicode delimited identifiers are supported in all SQL text statements. Please see the SQL Data Types and Literals manual for information on Unicode delimited identifiers.
The choice of the session character set imposes limitations on the support of object names. The .NET Data Provider Release 14.10 contains two changes to work around those limitations:
Two other areas of functionality in the Data Provider that are limited in the support of extended object names are:
Executing commands within TdCommandBuilder are recommended to use characters only representable within the current session character set or using a Unicode session character set, due to the limitation on extended object name representation within Teradata answer sets. Any characters that are not representable in the current session character set, will be returned by Teradata as translation error characters.
Visual Studio wizards and Visual Studio Server Explorer retrieve object names from Teradata by submitting requests that contain restrictions. The object name representation of these restrictions are limited by the current session character selected by the user. Any characters that are not representable in the current session character set, will be returned by Teradata as translation error characters. To fully support Visual Studio application wizards and Server Explorer, it is recommended to use a Unicode session character set.