---
sourceDocument: Australia Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/now-intelligence

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Database views for cross-table data

# Database views for cross-table data {#ariaid-title1}

Release version: Australia  
Updated March 25, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
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](https://www.servicenow.com/docs/0BmHD84G7z5nj9ylwlJX_g#gloss-database-view "A database view defines table joins for reporting purposes. For example, a database view can join the Incident table to the Metric Definition table. This view can be used for an indicator source.") in the [semantic layer](https://www.servicenow.com/docs/4q6x4QEhbrGjzdIOBwTbMw#gloss-semantic-layer "A flat representation of database tables and columns used by Query Generation to identify the correct data sources when processing a natural language question. The semantic layer consists of entities (tables), dimensions (columns), and segments (filter conditions).") enable you to answer questions that join data across tables in a single query instead of requiring separate questions or complex queries.{#database-views-cross-table-data__database-views-cross-table-data-para-1}

## When to use database views {#database-views-cross-table-data__section_b5w_hjj_s3c}

Use database views when:{#database-views-cross-table-data__database-views-cross-table-data-para-2}

* 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.
{#database-views-cross-table-data__ul_c5w_hjj_s3c}

## Implementation requirements {#database-views-cross-table-data__section_d5w_hjj_s3c}

When working with database views:{#database-views-cross-table-data__database-views-cross-table-data-para-3}

* You must be in the same application scope as the database view.
* Add database views to Semantic Table Configuration the same way as regular tables. You need 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 database views.
{#database-views-cross-table-data__ul_ud4_2ll_53c}
**Related tasks**   

* [Add a table to the semantic data layer](https://www.servicenow.com/docs/DnI5HK_x_33jozN_85GrWQ#add-table-semantic-layer "Add more tables to the Query Generation semantic layer so that users can use ServiceNow Otto for Platform Analytics applications to ask questions about the data in those tables.")