Amazon Redshift - Automatic Data Lineage
What to expect
Views
Dataedo analyzes SQL of Redshift views with built-in PostgreSQL Parser and builds column-level lineage from tables/views queried by view to the view.

Learn more about PostgreSQL parser
External Tables
Dataedo builds object-level lineage between Redshift External Tables and objects from other databases based on LinkedSources. Dataedo will automatically assign linked source to appropriate objects, however, the user can also pick it manually.

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.

Known Limitations
- Check the limitations for views lineage from PostgreSQL parser
- Check the limitations for stored procedures lineage from SQL parser
Troubleshooting
I don't see data lineage for views
- Make sure you have selected the right SQL dialect - in this case, PostgreSQL (SQL Dialect field at Data Source level).
- Rerun 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 external tables
- Make sure the source object has Linked Source with correctly assigned database.
- Rerun 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
- Make sure Dataedo supports SQL syntax of the procedure. Check Known Limitation above.
- 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
- Make sure the source object has Linked Source with correctly assigned database.
- Rerun import of the source - maybe the schema was imported in an older version or the configuration was incorrect.