16.10 - Unity Data Dictionary Requirements - Teradata Unity

Teradata Unity User Guide

Product
Teradata Unity
Release Number
16.10
Published
January 2018
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
anz1496162519675.ditamap
dita:ditavalPath
ft:empty

For Unity to manage objects across multiple Teradata systems, the objects must have identical attributes on each system. Unity updates the dictionary for any DDL statements that change tables and views.

This feature is not available with the Unity Passive Routing license.

Table Attributes

Unity considers a table the same across multiple Teradata Database systems when the following attributes are the same:
  • Database and table name
  • Number of columns, column names, and column order
  • Column data types, column default values, and nullability
  • Primary index
  • Unique, check, and RI constraints
  • Triggers
  • Whether the table allows duplicate rows
  • Table type (GLOBAL TEMPORARY TABLE, regular)
By default, the Unity Data Dictionary requires triggers on tables to be the same. However, you can manually allow different triggers across Teradata Database systems. For example, you can use a trigger to populate an unmanaged table that is only on a single Teradata Database system.

View Attributes

Unity considers a view the same across multiple Teradata Database systems when the following attributes are the same:
  • View and database name
  • All underlying objects are the same
  • View columns
  • Locking modifiers and column ordering
  • Query text
For the view to be managed as part of a dictionary, all dependent objects (such as tables) must be included in the deployed Unity Data Dictionary.

Stored Procedure Attributes

Unity considers stored procedures the same across multiple Teradata Database systems when the following attributes are the same:
  • Stored procedure name
  • All objects referenced in the procedure are managed
  • Order and number of arguments, data types, and direction
  • Read/Write/Call sets
  • SQL text
By default, the Unity Data Dictionary requires SQL text in the stored procedure to be the same.

Macro Attributes

Unity considers macros the same across multiple Teradata Database systems when the following attributes are the same:
  • Macro and database name
  • All underlying objects
  • Number of parameters, data types, and direction
  • Macro text
The Unity Data Dictionary also contains the following metadata:
  • If the object was manually added/edited or automatically generated (isGenerated flag).
  • If a stored procedure or function requires context from the sequencer.
The Unity Data Dictionary persists to non-production Teradata Databases and is stored in memory on each endpoint. If Unity receives DDL changes to tables, views, or macros in the Unity Data Dictionary, changes are made to the Unity Data Dictionary in the memory and persisted copy.