Database Reference
In-Depth Information
How it works...
The Creating dashboards from basic reports recipe is split into three parts. The combined
result of these parts is the final dashboard.
The breakdown of the parts is as follows
Creating the Open Incidents report : This first set of steps creates the data source
object that targets the Service Manager operational database. The dataset (query)
filters out the closed and resolved incidents. The filter is denoted by the GUID (in-
ternal name of the two status types).
Creating the Active Alerts report : This second set of steps creates the data
source object that targets the Operations Manager operational database. The dataset
(query) filters out the resolved alerts. The filter is denoted by Resolu-
tionState <> 255 (the value of the Operations Manager resolved state of an
alert).
Creating the combined dashboard : The third and final part of the recipe uses the
subreport option to create the dashboard. This is, in effect, a shortcut to the two re-
ports, and when executed, it renders the data and displays it as a single report.
The NOLOCK option is very important as the recipe accesses the operational databases.
This is a recommended practice to ensure that you do not impact the operational databases.
Tip
Develop in a test environment
We recommend that you use a test environment to develop and test your reports.
Search WWH ::




Custom Search