Hubert Książek
Dataedo will create column-level data lineage for stored procedures and user defined functions based on the script. Just leave the "Automatic lineage" option selected during import or doing import changes.
Dataedo will divide the procedure into steps and represent them as processes, then create a data lineage for supported steps. Unsupported steps will be named after the first word from the process script and end with three dots.
In the script tab, the processes contain fragments of the procedure script to which they refer.
Supported dialects
This function is available in the following dialects:
We are working on support for data lineage from stored procedures for other dialects.
Supported SQL syntax
We support the creation of an automatic lineage in all dialects for the following SQL statements:
SELECT INTO,INSERT,UPDATE,OUTPUT/RETURNstatements,- Not Recursive Common Table Expressions (CTE,
WITHstatements), CREATE TABLE AS SELECT.
When temporary tables are created in a procedure (ones that do not normally exist in the documented database), Dataedo will try to combine the lineage that goes into them with the lineage that comes out of them, i.e. instead of SOURCE_TABLE -> #TEMP_TABLE -> DESTINATION_TABLE, will represent it as SOURCE_TABLE -> DESTINATION_TABLE.
Regrettably, due to the nature of ANTLR, the presence of unsupported elements within a procedure may result in the entire procedure being unable to be parsed. In the current stage, we treat procedures incorporating elements beyond those explicitly outlined as unsupported. Nevertheless, we do our best to make sure that the unsupported elements do not affect supported steps.
We do not support the creation of an automatic lineage for the following SQL syntax:
DELETEstatements,BULK INSERTstatements,COPY INTOstatements,- Syntax mentioned as unsupported in the
SELECT/CREATE VIEWchapter.