Does iDBQuery replace my existing BI stack or work alongside it?
iDBQuery works alongside your existing BI stack rather than ripping it out — it connects to the same sources (including your warehouse) and answers the ad-hoc, cross-source and investigative questions dashboards weren't built for. Many teams keep their dashboards and add iDBQuery for everything in between.
You don't have to choose. BI tools like Power BI, Tableau and Looker are built for governed, repeatable dashboards — the standing reports everyone watches. iDBQuery is built for the questions those dashboards trigger but can't answer: the one-off, the cross-source, the 'why did this move.'
- It connects to the same data, including your data warehouse, so there's nothing to migrate.
- It fills the gap between dashboards — ad-hoc questions, exploration of unfamiliar sources, and reconciling numbers across systems.
- Cited answers give it audit-grade trust your dashboards may not expose.
- Cross-source by design. It joins databases, spreadsheets, PDFs and APIs that separate BI dashboards usually keep siloed.
- It can also produce reports and dashboards of its own, so for some teams it covers more of the stack over time.
Think of iDBQuery as the conversational, investigative layer over everything you already have. Keep your BI investment, point iDBQuery at the same sources, and give the whole team a way to ask questions in seconds without filing a request or building a new view. Replace later only if it makes sense — there's no forced rip-and-replace.
What each layer is actually for
| Your BI stack | iDBQuery | |
|---|---|---|
| Standing dashboards for a known audience | Yes — keep them | Not the job |
| The unplanned question at 4pm | A ticket and a wait | Answered now |
| Governed, certified metrics | Where governance belongs | Reads them; does not replace them |
| Questions spanning systems outside the warehouse | Requires a pipeline first | Queried in place |
| Tracing a figure to its source row | Varies by tool | Attached to every answer |
When the other one is the right choice
It does not replace your BI stack, and any vendor who tells you otherwise is selling. Dashboards that many people read every week should stay exactly where they are — that is what BI is good at. iDBQuery sits beside it for the questions those dashboards provoke and were never built to answer. The common pattern is both, and the honest test is whether your BI backlog shortens.
Updated 2026-08-08