Compatibility views convert the native variable length Unicode object names into 30 bytes of either Latin or Kanji1.This can cause loss of information by truncation or inability to convert object names longer than 30 characters into Latin or Kanji1. Characters that cannot be converted are replaced by the substitution character, which is 0x1A for both Latin and Kanji1.
As with all character data, when object names are returned to the user they are converted to the session character set. This conversion can produce loss of information if the characters in the object name cannot be converted to the session character set or exceed the export width for the character data.
Compatibility view names use the format:
Some non compatibility views also use this format and are not deprecated, such as BusinessCalendar.
For example, All_RI_Children or All_RI_ChildrenX, where the X denotes a partial view that omits restricted data, such as security-related information.
A Unicode view exists for every compatibility view in database DBC. The information available in compatibility views is available from the corresponding Unicode view, and compatibility views should no longer be used to obtain the required information.
Teradata strongly encourages you to switch over to Unicode views. The following compatibility views and compatibility X views are deprecated and will be eliminated in a future release.
In the following list, views ending in “[X]” indicate there is both a compatibility view and a compatibility X view; for example, DBC.AccountInfo and DBC.AccountInfoX are shown as DBC.AccountInfo[X].