Database Reference
In-Depth Information
However, in this case, we do not have the relational table corresponding to the
dimension that links the two measure groups. The following diagram describes
the situation we are modeling in our scenario. The dimension is created from
the
OrderNumber
and
LineNumber
fields in the fact table, forming a degenerate
dimension. For this reason, we cannot graphically represent the relationship
between the bridge table and the degenerate dimension.
Dim_SalesReasons
PK
ID_SalesReason
SalesReason
SalesReasonType
Fact_Sales
Bridge_OrdersSalesReasons
PK
ID_FactSales
OrderNumber
LineNumber
Value
PK,FK1
PK
ID_SalesReason
OrderNumber
We can model this relationship directly in our
Analysis Services
cube without
needing to materialize the degenerate dimension into a physical table. We already
have the
SalesReason
dimension defined in our cube, and we only need to add
a measure group corresponding to the bridge table
BridgeOrdersSalesReasons
defined in the
Sales
schema of our data mart. First of all, we will make this table
visible through a view, named
BridgeOrdersSalesReasons
in the
CubeSales
schema. Then, we add this table to the
Data
Source
view of our project, adding a
relationship between its
ID_SalesReason
field and the corresponding primary key
of the
SalesReasons
table, as in the following diagram:
BridgeOrdersSales...
ID_SalesReason
SalesOrderNumber
SalesReasons
ID_SalesReason
SalesReason
SalesReasonType
Search WWH ::
Custom Search