Why use iDBQuery instead of writing SQL by hand?
Writing SQL by hand means knowing the schema, the joins and the dialect, then debugging — iDBQuery writes correct, validated SQL from your plain-language question in seconds and runs it across all your sources at once. iDBQuery removes the time, expertise and error risk of hand-coding queries.
Hand-writing SQL is fine when you know the schema cold, but it's slow and error-prone the moment you hit an unfamiliar database, a cross-source join, or a dialect quirk. iDBQuery does the query authoring for you, then proves the result.
- From question to query instantly. Describe what you want in plain language; iDBQuery generates the SQL, including the right joins and filters.
- Across many sources at once. It builds one live model over your databases, spreadsheets, PDFs and APIs, so a single question can span all of them — no manual federation.
- Understands cryptic schemas. Its semantic layer learns what obscure table and column names actually mean, so you don't have to reverse-engineer them.
- Verifiable output. Every answer is cited back to the exact source rows, and you can inspect the generated SQL.
- No dialect juggling. It handles MySQL, Postgres and the rest, so you don't memorize each one's syntax.
For analysts who already know SQL, iDBQuery is a massive accelerator — it drafts the query, you review it. For everyone else, it removes the barrier entirely while still giving an answer you can audit.
Writing SQL yourself, or asking
| SQL by hand | iDBQuery | |
|---|---|---|
| Time to an answer | Minutes to hours, depending on the schema | Seconds |
| Who can do it | Someone who knows SQL and the schema | Anyone |
| Joining across systems | Manual, or not possible without a warehouse | One live model across sources |
| Reviewability | The SQL is right there | The SQL is shown, editable and re-runnable |
| Precise, unusual, or performance-critical queries | Full control | Best on questions a person would ask in words |
When the other one is the right choice
Keep writing SQL when the query is intricate, when you are tuning performance, or when you already know exactly the shape of the answer you want — you will get there faster yourself than by describing it. iDBQuery shows you the SQL it wrote precisely so that you can take over at that point rather than fight the tool.
Updated 2026-08-08