Netezza
Netezza is an on-premises data warehouse platform with massively parallel processing.
IBM Automatic Data Lineage can connect to the Netezza database via its own connection. It can scan the metadata and read all the SQL programming code and logic stored in it. Using this information, Automatic Data Lineage creates a detailed visualization of the data lineage that can be pushed to any third-party metadata management solution or viewed in Automatic Data Lineage native visualization.
Automatic Data Lineage currently scans: Tables, Views, Materialized Views, Procedures, Functions, Synonyms, Sequences, Netezza scripts, Columns, PseudoColumns.
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 Netezza servers, there are two scenarios.
-
Netezza dictionary mapping scenario — connects to each configured Netezza server and stores the mapping between these values: dictionary ID, host name, host port, include and exclude filters
-
Netezza extractor scenario — connects to each configured Netezza server and extracts the database dictionary and DDL scripts from the configured databases and their schemas
-
IBM Automatic Data Lineage supports Git Ingest connections from version 42.4, for the download of files from a Git repository to the Netezza workflow. For more information, see Manta Flow Agent Configuration for Extraction:Git Source
Analysis Phase
For the analysis phase for Netezza databases, there are three scenarios.
-
Netezza dictionary dataflow scenario — analyzes metadata from the extracted Netezza database dictionaries and saves it in your Automatic Data Lineage metadata repository
-
Netezza DDL dataflow scenario — harvests metadata and lineage from the extracted Netezza DDL scripts and saves it in your Automatic Data Lineage metadata repository
-
Netezza PL/SQL dataflow scenario — harvests metadata and lineage from the provided Netezza PL/SQL scripts