A database view defines table joins for reporting purposes.
For example, a database view can join the Incident table to the Metric Definition and Metric
Instance tables. This view can be used to report on incident metrics and may include fields from
any of these three tables.
A number of useful database views are installed with the Database View plugin and the Database
Views for Service Management plugin. These database views cover most metric reporting needs and
greatly reduce the need to define new ones.
Note: In general, as the number of tables that are included in the view and the number of records
that those tables contain increases, the accumulated impact on performance grows. In addition,
to optimize the performance of the database view ensure that the ‘where’ clauses that are
defined in the database view are based on indexed fields.
- Database views cannot be created on tables that participate in table rotation.
- It is not possible to edit data within a database view.
ACLs and database views
You need to create a read ACL for your users on the tables in a view to generate reports on
database views. Non-admin users do not have access to database view records unless a read ACL on
the database view record allows access. For information about table-level and field-level ACL
behavior on database views, see the ACL on Database Views [KB0535471] article in the HI Knowledge Base.