Can I connect a database to iDBQuery over ODBC or JDBC?

If you're used to reaching a database through ODBC or JDBC, the mental model carries straight over: iDBQuery connects to the same standard SQL databases and warehouses those drivers target, using the usual connection details.

• You'd connect by entering the host, port, database/schema and a read-only user — the identical coordinates an ODBC/JDBC data source needs.
• iDBQuery introspects the tables and columns, applies its semantic layer to interpret naming, and adds the database to your one live queryable model.
• Then you ask in plain language and iDBQuery writes the SQL, runs it, and returns a cited answer, chart or dashboard.

This covers the common SQL engines — MySQL, PostgreSQL, SQL Server, Oracle, MariaDB, SQLite — and SQL warehouses such as Snowflake, BigQuery, Redshift and Databricks, all through the standard warehouse/database connector rather than a per-vendor bespoke build. The point of difference is what happens after connecting: instead of a driver just returning rows to a BI tool, iDBQuery lets anyone ask in plain language, queries in place, and cites every figure back to its source rows. You can also blend that database with other connected sources in a single question — one model, no ETL. For databases behind a firewall, deploy iDBQuery in the same VPC or air-gapped so the connection stays private.