Compatibility Considerations | Teradata Unity - ​​​​Compatibility Considerations - Continuous Availability - Teradata Unity

Teradata® Unity™ Compatibility Matrix

Continuous Availability
Teradata Unity
January 2022
English (United States)
Last Update
Product Category
Analytical Ecosystem

17.00 Series

The following compatibility observations apply to Unity 17.00 with Vantage 2.0. Unity 17.00 with Vantage 1.0 behaves as Unity 16.51.
  • Unity does not support load jobs with non-deterministic DML.
  • Due to recovery limitations, the use of volatile tables (VT) and global temp tables (GTT), in Unity-managed systems should be limited. Unity does not support non-deterministic write requests to VT/GTTs. Deterministic write requests to VT/GTTs are not recoverable if a failure happens after the population of the VT/GTT and before all writes using the VT/GTT have completed.
  • Unity does not change routing rules based on alternative current users defined in Query Bands.
  • ​​Unity does not replicate changes applied via sessions connected directly to Vantage outside of Unity.​
  • Unity does not replicate object names, including usernames, when the name includes: periods, single quotes, and spaces.
  • Unity does not replicate sessions using Teradata Secure Zones.
  • Unity does not replicate sessions issuing QueryGrid, SQL-H, or Foreign Server requests.
  • Unity does not support debugging of User Defined Functions (UDF).
  • Unity does not support Extended Multiload (MloadX).
  • Unity does not support directly selecting from join indexes.
  • Unity does not support load isolation.
  • Unity does not support mainframe clients.
  • Unity does support up to 1 Million objects in managed dictionaries.
  • Unity does not support statement independence.
  • Unity does not support TDNEGO authentication.
  • Unity does not support Unicode pass-through characters.
  • Unity does not synchronize DBQL objects as they are system-specific.
  • Unity does not support Fastload for the Teradata SQL Driver for Python.
  • Unity rolling upgrades to version and later from versions earlier than is not allowed.
  • Unity requires all system-specific statements to be executed using system-specific session routing rules.
  • Unity requires all managed Vantage systems and Unity servers to have the date-and-time and time zone synchronized via NTP or similar service.
  • Unity requires all managed Vantage systems to have CDM enabled to replicate statements using non-deterministic functions.
  • Unity requires Proxy-Authorization to be enabled in all managed Vantage systems if TD2 authentication is not in use.
  • Unity requires CDM to be enabled in order to issue CREATE/REPLACE PROCEDURE requests which are greater than 1MB in size.
  • Unity uses CDM to replicate statements that use Identity columns and requires Identity columns to be defined such that they have different ranges on different systems.
  • Unity supports the following character sets: ARABIC1256_6A0, ASCII, EBCDIC, LATIN1250_1A0, LATIN1252_3A0, LATIN1254_7A0, LATIN1258_7A0, LATIN1258_8A0, LATIN9_0A, LATIN1_0A, THAI874_4A0, UTF8, and UTF16.

Differences between 17.00 and 16.51 Series

  • Unity replicates non-deterministic use of CREATE TABLE AS statements.
  • The Unity dictionary now supports up to 1 million objects from the previous limit of 500,000.

Differences between 16.51 and 16.50 Series

  • Support for additional character sets: LATIN1250_1A0

Differences between the Unity 16.50 and the Unity 16.20.33 Series

New observations:
  • Rolling upgrades to versions and later from versions earlier than is not supported.
  • The Unity dictionary now supports up to 500,000 objects.

CDM replication no longer has a 20GB change data limit for transaction.