Glossary

Explore Meshline

Products Pricing Blog Support Log In

Ready to map the first workflow?

Book a Demo

Glossary / Evaluation and implementation guide

Data Lineage

Data lineage is the recorded map of how data moves and changes between systems: which sources feed which tables, which transformations apply, and which dashboards consume the results. Vendors differ sharply in capture depth.

Table-level lineage shows dependencies between datasets; column-level lineage traces individual fields through transformations, which is what impact analysis and root-cause work actually require.

A practical example

Example: when a revenue column's logic changes, column-level lineage should show every downstream metric, report and alert affected, so the team can notify owners before numbers shift.

What to evaluate before investing

  • Ask whether lineage is parsed from code like SQL and dbt, inferred from query logs, or declared manually, and how each mode handles dynamic SQL.
  • Verify column-level lineage exists for your transformation layer, not just table-level edges between systems.
  • Test how lineage updates when pipelines change: delayed or stale graphs undermine trust during incidents.

Limitations and tradeoffs

Lineage graphs are only as complete as their capture method; log-based approaches miss logic outside queries, and manual approaches go stale, so coverage claims deserve scrutiny.

Plan your next step with MeshLine

Connect this decision to your automation, organic marketing and customer lifecycle management. In a MeshLine demo, discuss your existing tools, the scope you need and how to measure the result.