Is iDBQuery a semantic layer?
Not exactly — iDBQuery includes a semantic layer, but it is more than that. The semantic layer helps it understand cryptic table names, business terms and metrics; on top of it, iDBQuery writes SQL, runs queries and returns cited answers, charts and dashboards.
A semantic layer is a map of business meaning that sits over raw tables — defining what a 'customer', a 'region' or 'net revenue' actually is. iDBQuery has one built in, but it is a whole querying experience, not just the map.
- The semantic layer does the interpreting. It links cryptic columns and codes to real business concepts, resolves synonyms and understands metrics, so you can ask in your own words.
- iDBQuery does the answering. On top of that meaning, it writes the SQL, runs it against your live data, and returns a cited number, chart or dashboard in seconds.
- It self-builds. iDBQuery bootstraps the semantic layer automatically when it introspects a source, so you are not forced to define every metric by hand before you start.
With a standalone semantic layer product, you still need a BI tool on top and someone to model everything first. iDBQuery combines the two: the meaning and the answers come together. For example, you can ask 'what was net revenue by region last month?' and iDBQuery uses the semantic layer to know exactly which tables, filters and joins that implies — then shows you the SQL and the source rows so you can trust the result.
Updated 2026-06-22