Database Reference
In-Depth Information
Getting ready
It is recommended that you read the
Understanding the OperationsManagerDW schema
re-
cipe earlier in this chapter before following this recipe. You will need to prepare your en-
vironment to author reports by following the instructions in the
Preparing your environ-
ment to author reports
recipe.
Before we start authoring our report, we will take a look at the views that are available in
the event dataset in the
OperationsManagerDW
database.
Event dataset
The event dataset can be used to retrieve information about the events collected from mon-
itoring objects by
Operations Manager Event Collection Rules
. The event dataset in-
cludes four views that represent the data. All views are stored in the
Event
database
schema.
Event.vEvent
The
Event.vEvent
view contains all the events available in the
OperationsMan-
agerDW
database. Apart from information such as the event unique ID, event number, and
event date/time, it also includes other unique IDs that can be joined to more views to re-
trieve additional information about the events.
The
Event.vEvent
view can be joined to the other views in the event dataset on the
EventOriginId
column.
You can join more views to the
Event.vEvent
view using the unique IDs available in
the view, as outlined in the following table:
View
Join
Description
Event.vEvent.EventCategoryRowId = vEventCat-
egory.EventCategoryRowId
vEventCategory
This is the event category information
This is the channel of the event, such
as application, system, or the name of
a custom event collection rule
Event.vEvent.EventChannelRowId = vEventChan-
nel.EventChannelRowId
vEventChannel
