Lineage Scan is Creating two assets for a view - a table and a view, with portions of the data for the asset on each

Question

When running my lineage scan in Purview there are some instances where a view has created a table and a view. The schema exists on the view, with no lineage found. But the lineage exists on the table, with no schema found.

I've allowed lineage scans to continue run via incremental, but the issue doesn't seem to be fixing itself.

Answer 1

Hi @Sarah Tout

Welcome to Microsoft Q&A platform and thanks for posting your query here.

This is a known limitation in Microsoft Purview. When a database view is used as a source in process activities (such as Azure Data Factory, Synapse Pipelines, Azure SQL Database, or Azure Data Share), it is captured as a table with lineage. Meanwhile, if the database is also scanned, the view asset is discovered separately with its schema but without lineage. As a result, you may see two assets with the same name:

• A Table with lineage but no schema
• A View with schema but no lineage

Since this is expected behavior, incremental scans will not change the result. For more details, you can refer to the official Microsoft documentation: Data lineage user guide

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

Thank you.