What is a database view?
A database view is a saved query that behaves like a virtual table: it has a name and columns, but its data is computed on demand from underlying tables rather than stored separately. Views simplify complex joins, standardise business logic and can restrict which columns users see.
A view lets you package a query, say, orders joined to customers with revenue calculated, behind a simple name. Query the view like a table and the database runs the underlying SQL for you.
Views are used to:
- Simplify hide complex joins and calculations behind one object.
- Standardise define a metric once so everyone uses the same logic.
- Secure expose only certain columns or rows to certain users.
- Abstract shield reports from changes in the physical schema.
Because a standard view computes on read, it always reflects current data (a materialized view instead stores results and refreshes on a schedule).
iDBQuery treats your existing views as first-class sources: it can query a view exactly as it queries a table, so any business logic you have already encoded there is respected in its answers. And for the many teams that never got around to building views, iDBQuery offers the same simplicity from the other direction, ask in plain language and it assembles the joins and calculations on the fly, no view to define first, with every figure cited back to its source rows.
Updated 2026-06-22