Database views for cross-table data
Database views combine fields from multiple tables into a single queryable entity. Add views to the semantic layer to answer cross-table questions in one query instead of requiring separate questions.
Database views in the semantic layer enable you to answer questions that join data across tables in a single query, rather than requiring separate questions or complex queries.
When to use database views
Use database views when:
- Users ask questions that join data across tables, such as incidents and changes
- A cross-table report already exists as a database view
- The same fields from different tables keep appearing together in user questions
Implementation guidelines
Follow these guidelines when working with database views:
- Views are added to Semantic Table Configuration the same way as regular tables, requiring the sn_query_gen.admin role or higher.
- Dimension names include a source-table prefix, such as inc_number or chg_priority
- Entity descriptions are auto-generated from the source tables and update automatically
- The Include child hierarchy setting has no effect for views