Skip to main content

About the Teradata collector

Important

The Teradata collector can be run on-premise using Docker or Jar files.

Note

The latest version of the Collector is 2.189. To view the release notes for this version and all previous versions, please go here.

Use this collector to harvest metadata from Teradata including user defined functions, stored procedures, triggers, user defined types and user defined methods.

What is cataloged

The collector catalogs the following information.

Note

The collector harvests all versions of overloaded functions and stored procedures. Each version has its own title/name in the catalog, but a distinct identifier.

Table 1.

Object

Information cataloged

Database

Type, Name, Description, JDBC URL, Owner name, Space allocation (permanent, spool, temporary), Created By, Created At, Updated By, Updated At

Table

Name, Description, Primary Key, Foreign key, Size, Created By, Created At, Updated By, Updated At

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, Description, Function type, Definition, Number of parameters, Source file language, Data access, Parameter style, Deterministic characteristic, Null-call characteristic, Execution protection mode, Character type, Platform type

SQL stored procedures

Name, Description, Stored procedure type, Definition

External stored procedures

Name, Description, Stored procedure type, Definition, Number of parameters, External file reference, Source file language, Data access, Parameter style,  Execution protection mode, Character type, Platform type, Application category

Triggers

Name, Description, Definition, Trigger enabled, Order number, Fired at instant, Fired on event, Evaluation type, Created By, Created At, Updated By, Updated At

User defined types

Name, Type, Default transform group, Instantiable, Final, Encryption supported, Compression supported, All operators supported, Ordering form, Ordering Category, Default null specified for array

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



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 with the help of the data.world Solutions team, you may see other resource pages and relationships.

Table 3.

Resource page

Relationship

Table

  • Columns contained in tables

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 following lineage information is collected by the Teradata collector.

Table 4.

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 tables updated.

NOTE: Lineage is not available when the SQL Statement in Stored Procedures contains the SELECT INTO clause.



Authentication supported