How does iDBQuery build one live model from all my sources?
iDBQuery builds one live queryable model by introspecting every connected source and federating them into a single virtual layer you can query together. There is no warehouse to provision and no pipeline to maintain — your databases, spreadsheets, PDFs and APIs become one model that always reflects the live data underneath.
Most analytics setups force you to copy everything into a central warehouse first, then build pipelines to keep it fresh. iDBQuery skips that. When you connect a source, it reads the structure and registers it in a federation layer. A second source joins the same layer, and a third — each keeping its own native shape.
When you ask a question that touches more than one source, iDBQuery plans a query across the whole layer at once, pulling exactly what it needs from each system in place. The result is one live model:
- It spans databases, spreadsheets, documents and APIs together.
- It stays current because it reads the underlying sources at query time, not a stale snapshot.
- It needs no warehouse, no nightly ETL job and no schema design work from you.
A semantic layer sits on top to reconcile naming differences between sources, so a customer in one system lines up with the same customer in another. The practical upshot: you can ask one question that spans several systems and get a single answer, with every number still traceable to the exact source it came from.
Updated 2026-06-22