Can I connect a DuckDB database to iDBQuery?
Yes. iDBQuery reads a DuckDB database as a local SQL source, so you can ask plain-language questions of its tables and get cited answers. You can also point iDBQuery at the Parquet or CSV files behind DuckDB and query them the same way.
DuckDB is a lightweight, file-based analytical database, popular for fast local analytics over Parquet and CSV. iDBQuery can read a DuckDB database as a SQL source: it introspects the tables, understands the schema through its semantic layer, and lets you ask questions in plain language.
Two common paths:
- Point at the DuckDB file — iDBQuery reads its tables directly and writes the SQL for you.
- Point at the underlying files — if your data lives as Parquet or CSV that DuckDB sits on top of, iDBQuery can ingest those directly too.
Either way you get iDBQuery's core promise: cited answers. Ask 'average order value by month' and every figure links back to the exact source rows, so you can verify it.
Example: a data scientist keeps a local DuckDB file of experiment results. Rather than writing SQL by hand, they ask 'which variant had the highest conversion at 95% confidence?' and get a readout in seconds.
Because DuckDB is often used locally, this pairs well with iDBQuery's Desktop app, which keeps everything on your machine — nothing has to touch the cloud. And you can join your DuckDB data with a live Postgres database, a spreadsheet, or an API in a single question, forming one live model across all of them.
Updated 2026-06-22