MySQL, MariaDB, SingleStore

MySQL, MariaDB, and SingleStoreDB are relational SQL database systems, and Automatic Data Lineage MySQL scanner supports all three. Once configured, the scanner can connect to the MySQL-based resource and automatically extract and analyze the relevant metadata from the selected databases/schemas (in MySQL, the terms 'database' and 'schema' refer to the same concept).

Automatic Data Lineage currently scans (dictionary information only, no lineage):

• Information about database entities through the information_schema

  • Tables

  • Views

  • Procedures

  • Functions

  • Events

  • Triggers

  • Sequences

  • Pipelines

Check out the guidelines below for more details on setting up this scanner.

• MySQL Integration Requirements
• MySQL Resource Configuration

Extraction and Analysis Phase Scenarios

Extraction Phase

For the extraction phase for MySQL-based database servers, there are two scenarios.

1. MySQL dictionary mapping scenario - connects to each configured MySQL-based database server and stores the mapping between these values: dictionary ID, subdialect, host name, port, included databases/schemas, and excluded databases/schemas

2. MySQL extractor scenario - connects to each configured MySQL-based database server and extracts the database dictionary and DDL scripts from the configured databases/schemas

3. IBM Automatic Data Lineage supports Git Ingest connections from version 42.4, for the download of files from a Git repository to the MySQL workflow. For more information, see Manta Flow Agent Configuration for Extraction:Git Source

Analysis Phase

For the analysis phase for MySQL-based database servers, there is currently single scenario.

1. MySQL dictionary dataflow scenario - analyzes metadata from the extracted MySQL-based database dictionaries and saves it in your Automatic Data Lineage metadata repository.

Related Articles

• Dictionary Dataflow Scenario Fails with java.langOutOfMemory: Java heap space

• How to Handle Dynamic SQL Scripts