Each OLAP cube contains a collection of facts that exist in
the data mart, where each member in the collection corresponds to a
measure group. Each measure group must have its own unique name within the OLAP
cube. However, a single fact may correspond to multiple measure groups in an
OLAP cube. For example, the abstract relationshipWorkItemAssignedToUser may
be defined three times in an OLAP cube, with the unique measure group names
of ChangeRequestAssignedToUser, IncidentAssignedToUser,
and ProblemAssignedToUser. As described in the in the Substitution section,
you can customize the fact so that only change requests, incidents, and
problems are included in the respective measure group for the OLAP cube.
The following example shows the management pack element for the
IncidentAssignedToUser measure group:
<MeasureGroup
DateDimAlias="IncidentAssignedToUserDateDim"
MeasureGroupName-"IncidentAssignedTouser"
Fact="DWBase!WorkItemAssignedToUserFact"/>
When the OLAP cube is deployed, the dimension, outriggers, and
foreign key relationships are automatically calculated and the data
source view will be updated with these new elements. The following table
describes measure group attributes.
Attribute
|
Required
|
Values
|
Definition
|
DateDimAlias
|
No
|
String
|
The name of the date dimension that
will filter on this measure group. If no alias is defined, the date dim role
playing name will automatically be "(MeasureGroupName)_DateDim"
|
MeasureGroupName
|
Yes
|
String
|
The name of the measure group in
the cube. This name must be unique within the cube.
|
Fact
|
Yes
|
Relationship or CustomFact
|
The target of the measure group,
which must be a fact in the data warehouse.
|
No comments:
Post a Comment