Teradata metadata collector

The Teradata metadata collector harvests read-only metadata from a Teradata account.

The collector harvests metadata from Teradata, including user defined functions, stored procedures, triggers, user defined types, and user defined methods.

Authentication supported

The collector authenticates to Teradata using username and password. Before running the collector, set up a dedicated database user with the required permissions. See Prepare to run the Teradata Collector.

Metadata cataloged

Table 1. Teradata metadata cataloged by object type

Object	Information cataloged
Database	Type, Name, JDBC URL Extended metadata: Created By, Created At, Updated By, Updated At, Owner name, Space allocation (permanent, spool, temporary), Description
Table	Name, Description, Primary Key, Foreign Key, Sample rows (if data sampling is enabled) Extended metadata: Created By, Created At, Updated By, Updated At, Size
Table index	Index Cardinality, Column name, Index Type, Index Name, Is Non Unique, Column Ordinal Position, Pages, Column Sort Sequence
Schema	Name
Column	Name, Description, Data Type, Is Nullable
View	Name, Description, SQL definition, Created By, Created At, Updated By, Updated At
User defined functions	Name, Function type Extended metadata: Definition, Deterministic characteristic, Null-call characteristic, Description, Number of parameters, Source file language, Data access, Parameter style, Execution protection mode, Platform type, Character type, Created, Created By, Last Modified, Last Modified By, External File Reference
SQL stored procedures	Name, Description, Stored procedure type, Definition Extended metadata: Created, Created By, Last Modified, Last Modified By
External stored procedures	Name, Stored procedure type Extended metadata: Definition, Application category, Description, Number of parameters, External file reference, Execution protection mode, Character type, Platform type, Source file language, Parameter style, Data access
Triggers	Name, Fired at instant Extended metadata: Created By, Created At, Updated By, Updated At, Name, Evaluation type, Fired on event, Trigger enabled, Order number, Definition, Trigger Comment, Subject Table Name, Action Time, Trigger Definition
User defined types	Extended metadata: Name, Type, Default transform group, Ordering form, Ordering Category, Default null specified for array, All operators supported, Encryption supported, Compression supported, Instantiable, Final
User defined methods	Name, Description, Number of parameters, Source file language, Data access, Parameter style, Deterministic characteristic, Null-call characteristic, Execution protection mode, Character type, Platform type

Profiling and sampling specific information.

If you include the profiling and sampling specific parameters while running the collector, the following additional information is harvested for columns.

Note:

Users or roles must have read access to data to harvest profiling information (column statistics).

Table 2. Profiling and sampling metadata cataloged by object type

Object	Information cataloged
Column	Average Length (sample) Average Value (sample) Data Distribution Distinct Values Estimated Distinct Values Estimated Non-null Values Maximum Length (sample) Maximum Value (sample) sorted numerically or alphabetically (z–a) Minimum Length (sample) Minimum Value (sample) sorted numerically or alphabetically (a–z) Non-null Values (sample) Sample String Values (first 5 items in a column)
Table	Row Count Sample Count (target sample size)

Relationships between objects

By default, the harvested metadata includes catalog pages for the following resource types. Each catalog page has a relationship to the other related resource types. If the metadata presentation for this data source has been customized, you might see other resource pages and relationships.

Table 3. Teradata resource page relationships

Resource page	Relationship
Table	Columns contained in tables Table indexes
Columns	Table Table indexes
Table indexes	Columns
Trigger	Table triggers on tables
Schema	Database that contains schema Table that is part of schema
Database	Schema contained in database

Lineage for Teradata

The Teradata collector collects the following lineage information.

Note:

Lineage for SQL statements defined via variable statements is not supported.

Table 4. Teradata lineage by object type

Object	Lineage available
View	The collector identifies the associated column in an upstream view or table: Where the data is sourced from That sort the rows via ORDER BY That filter the rows via WHERE/HAVING That aggregate the rows via GROUP BY
Stored procedure	The collector identifies: The associated column in an upstream view or table Where the data is sourced from That sort the rows via ORDER BY That filter the rows via WHERE/HAVING That aggregate the rows via GROUP BY The downstream table that has its data updated Lineage is not available in the following cases: The SQL statement in stored procedures contains the SELECT INTO clause Stored procedures with multiple insert statements Stored procedures used to create tables or transient tables created during the execution scope of a stored procedure

• Prepare to run the Teradata Collector
  Create a dedicated Teradata user with the permissions required for the metadata collector to harvest metadata from a target database.
• Create a Teradata metadata collector
  Create a collector to import metadata from Teradata.