MySQL - Automatic Data Lineage

What to expect

Views

Dataedo analyzes SQL of database views with built-in SQL Parser and builds column-level lineage from tables/views queried by view to the view.

(/data-sources/sql-parser/mysql-parsing)

Stored Procedures

Dataedo will create column-level data lineage for stored procedures based on the script. The script will be divided into steps represented as separate processes. Data lineage will be created only for supported steps; the unsupported steps will be named after the first word from the process script and end with three dots.

When the connecting line between elements is selected, the details of the data flow are displayed, including the script fragment responsible for that flow.

SQL Queries (SELECTs in procedures)

If a stored procedure returns a table, a SQL Query object will be created in the documentation to represent the output. Dataedo will generate column-level data lineage between the source objects and the SQL Query based on the procedure script. The stored procedure will act as the processor in this lineage, connecting input sources with the resulting query output.

Known Limitations

1. Check the limitations for views lineage from MySQL parser

Troubleshooting

I don't see data lineage for views

1. Make sure you have selected the right SQL dialect - in this case MySQL

2. Rerun import of the source - maybe the schema was imported in an older version or the configuration was incorrect

Cross database lineage is not built

1. Make sure the source object has Linked Source with correctly assigned database

2. Rerun import of the source - maybe the schema was imported in an older version or the configuration was incorrect