Skip to main content

About the Teradata collector

Important

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

Note

The latest version of the Collector is 2.247. 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, 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

Extended metadata: Created By, Created At, Updated By, Updated At, Size

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



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.

Note

Any lineage for SQL Statements defined via variable statements are not supported.

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.

  • Stored procedures with multiple insert statements are not supported

  • Stored procedures used to create tables or any transient tables created during the execution scope of a stored procedure.



Authentication supported

In this section: