View basic lineage from metadata objects

Start with a table, column, or report to understand its sources and destinations. Available relationships depend on harvesting, lineage parsing, and object matching; names alone do not establish lineage.

View lineage

1. Find the object in Datasets or Reports.
2. Open the lineage relationships or analysis area in details.
3. Verify its source and name, then inspect upstream and downstream nodes and edges.
4. Follow upstream paths to trace origins or downstream paths to assess change impact.
5. Open important nodes in metadata details to verify physical identity and meaning.

Column and table lineage have different granularity. Table relationships alone do not establish how a column is calculated.

If no relationships appear

Check harvesting, lineage file parsing, namespace and schema matching, then resource synchronization. An empty graph can indicate incomplete preparation rather than no business dependencies.

Understand the SQLink boundary

Lineage management and end-to-end lineage viewed from metadata belong to metadata lineage. Lineage maps and application scenarios in the standalone Data Lineage section belong to SQLink and require the corresponding capabilities.

Administrators maintain harvesting, spaces, namespaces, and preprocessing. See Lineage administration. SQLink analysis is not a default metadata capability.