SQL Server - Automatic Data Lineage

What to Expect

Views

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

Learn more about Transact-SQL SQL parser

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. This is seen on the data lineage configuration tab in Desktop.

Polybase (external tables)

Dataedo will create object-level data lineage for Polybase connections. Dataedo supports the following sources:

• Oracle
• MongoDB
• Azure Data Lake Storage (ADLS) and Azure Blob Storage
• SQL Server
• S3-compatible object storage

Known Limitations

1. Check the limitations for views lineage from SQL parser
2. Check the limitations for stored procedures lineage from SQL parser

Troubleshooting

I don't see data lineage for views

1. Make sure you have selected the right SQL dialect - in this case Transact-SQL (SQL Dialect field at Data Source level).
2. Rerun the import of the source - maybe the schema was imported in an older version or the configuration was incorrect.

I don't see data lineage for stored procedures

1. Make sure Dataedo supports the SQL syntax of the procedure. Check Known Limitations above.
2. Rerun the import of the source - maybe the schema was imported in an older version or the configuration was incorrect.

I don't see data lineage for Polybase

1. Make sure the source object has a Linked Source with a correctly assigned database.
2. Rerun the 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 a Linked Source with a correctly assigned database.
2. Rerun the import of the source - maybe the schema was imported in an older version or the configuration was incorrect.