Is iDBQuery a replacement for SQL?
Yes for most everyday questions — iDBQuery writes the SQL for you from a plain-language question, so you rarely need to write it yourself. SQL still runs underneath, and iDBQuery shows you the exact query it used, so technical users can inspect or reuse it.
iDBQuery does not get rid of SQL — it writes it for you, so you no longer have to. For most business questions, that means you never touch SQL again.
- You ask, it writes. Type 'top 10 customers by revenue this year' and iDBQuery generates and runs the correct SQL against your live data.
- SQL stays visible. It shows the exact query it used, so analysts and engineers can review, edit or reuse it — nothing is hidden.
- It handles the hard parts. Joins across tables, date logic, fiscal calendars and cryptic column names are inferred by the semantic layer, which is where hand-written SQL usually goes wrong.
So who still benefits from SQL? Power users who want to fine-tune a query, or embed it elsewhere, keep full control. But the analyst who used to be the bottleneck for every ad-hoc request is freed up, and non-technical colleagues get answers without waiting. For example, a finance manager can self-serve 'AR aging by customer' in seconds, while a data engineer can open the generated SQL to confirm the logic. iDBQuery replaces the need to write SQL, not the transparency of it.
Updated 2026-06-22