![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a fact with ProductSKU level measures for the Product dimension. But I need to load the cube with the next level up of data for the Product dimension which is ProductType level (The hierarchy is already there in the Product dimension). Is there a way for SSAS to suck the fact data without storing the leaf in the cube? |
#3
| |||
| |||
|
#4
| |||
| |||
|
#5
| |||
| |||
|
|
Just remove the leaf from the DataSourceView. The cube can't store what it doesn't know about. You may need to add a named calculation for the ProductType totals. The only issue I see by doing this, is that the granularity may be compromised if the FK's to the Dimension tables are at the SKU level, you may not have a key to keep the fact and dim's in synch. So you may need to insure that keys at the Type level will hold the dimensions in synch. HTH Steve Muise Neudesic LLC |
#6
| |||
| |||
|
|
Well typically I just use a view with "group by" to get next level aggregate. But it would be nice if SSAS had an option where you can say you want to "physically" persist a certain level. Steven.Muise (AT) gmail (DOT) com wrote: Just remove the leaf from the DataSourceView. The cube can't store what it doesn't know about. You may need to add a named calculation for the ProductType totals. The only issue I see by doing this, is that the granularity may be compromised if the FK's to the Dimension tables are at the SKU level, you may not have a key to keep the fact and dim's in synch. So you may need to insure that keys at the Type level will hold the dimensions in synch. HTH Steve Muise Neudesic LLC |
![]() |
| Thread Tools | |
| Display Modes | |
| |