Can I connect only a specific schema or subset of tables to iDBQuery?
Yes. You don't have to expose an entire database — you can scope iDBQuery to a specific schema or a chosen set of tables. Combined with a read-only user, this lets iDBQuery see only the data you want it to query, and nothing else.
Big databases often contain far more than you want an analytics tool to touch — internal system tables, other teams' schemas, or sensitive columns. iDBQuery lets you limit the scope so it only sees the data you choose.
Two complementary ways to control it:
- At the database — give iDBQuery a read-only user whose grants cover only the relevant schema or specific tables. The database itself then enforces the boundary; iDBQuery literally cannot see the rest.
- In iDBQuery — point the connection at a particular schema or select the tables you want included in your model.
Scoping down has real benefits beyond security. A focused set of tables means the semantic layer and query generation stay sharp and fast, because iDBQuery reasons over the tables that matter instead of thousands of irrelevant ones. It also keeps answers relevant to the business area you care about.
Example: a company's warehouse has 40 schemas, but the finance team only needs the general-ledger schema. They grant iDBQuery read access to just that schema, and finance gets cited answers over exactly their data — with no path to anything else. You can always widen the scope later by extending the grants or adding tables to the model.
Updated 2026-06-22