Teradata
IBM Manta Data Lineage provides a powerful scanner for Teradata Database. Manta Data Lineage can connect to Teradata Database via its own connection and automate metadata scanning within the selected views, macros, and stored procedures (SQL). Manta Flow supports data dictionaries, SQL, BTEQ, stored procedures, macros, TPT, and database query logs. Manta Data Lineage can generate lineage at the lowest granularity while showing all data transformations throughout the pipeline.
Manta Data Lineage currently scans:
-
Database dictionaries
-
Stored procedures
-
BTEQ scripts
-
TPT scripts
-
Views
-
Macros
Check out the guides below for more details on setting up this scanner.
Extraction and Analysis Phase Scenarios
Extraction Phase
For the extraction phase for Teradata databases, there is only one scenario.
-
Teradata extractor scenario — connects to each configured Teradata database and extracts the database dictionary and DDL scripts from the configured schemas
-
IBM Manta Data Lineage supports Git Ingest connections from version 42.4, for the download of files from a Git repository to the Teradata workflow. For more information, see Manta Flow Agent Configuration for Extraction:Git Source
Analysis Phase
For the analysis phase for Teradata databases, there are four scenarios.
-
Teradata dictionary dataflow scenario — analyzes metadata from the extracted Teradata database dictionaries and saves it in your Manta Data Lineage metadata repository
-
Teradata DDL dataflow scenario — harvests metadata and lineage from the extracted Teradata DDL scripts and saves it in your Manta Data Lineage metadata repository
-
Teradata BTEQ dataflow scenario — harvests metadata and lineage from the provided BTEQ scripts
-
Teradata Parallel Transporter dataflow scenario — harvests metadata and lineage from the provided TPT scripts