What is data lineage?
Data lineage is the record of where data comes from and how it moves and transforms as it flows through systems — so you can trace any figure back to its origin. iDBQuery gives you lineage at the answer level: every number it returns is cited straight back to the exact source rows it came from.
Data lineage answers the question "where did this number come from?" It's the traceable map of data's journey — which source it originated in, what transformations and joins it passed through, and how it ended up in the report on your screen. Good lineage matters for trust and governance: when a figure looks wrong, or an auditor asks you to justify it, lineage is what lets you follow the trail back instead of shrugging.
In traditional stacks, lineage is a whole discipline, because data has usually been copied and reshaped through many ETL steps before it reaches a dashboard, and reconstructing the path is hard.
iDBQuery makes lineage a built-in property of every answer rather than a separate project:
- Cited answers are lineage. Each figure in a response links back to the specific rows and source system it was drawn from, so the provenance is the answer, not an afterthought.
- It's the real path, not a guess. Because iDBQuery writes and runs actual queries against your live sources, the citation reflects exactly which data the result touched.
- Fewer hidden hops. Since iDBQuery queries in place instead of pushing data through layers of pipelines, there are far fewer opaque transformations between source and answer to lose track of.
So when a board report says a metric moved by 14%, iDBQuery lets anyone click through to the underlying rows — turning "trust me" into verifiable lineage on demand.
Updated 2026-06-22