dbTalk Databases Forums  

Loading Cubes for SSAS

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss Loading Cubes for SSAS in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
ricocali@hotmail.com
 
Posts: n/a

Default Loading Cubes for SSAS - 09-24-2005 , 11:13 AM






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?


Reply With Quote
  #2  
Old   
Jéjé
 
Posts: n/a

Default Re: Loading Cubes for SSAS - 09-25-2005 , 02:12 PM






try to disable the product level in the cube.

in this case type level become the lowest level.

<ricocali (AT) hotmail (DOT) com> wrote

Quote:
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?




Reply With Quote
  #3  
Old   
ricocali@hotmail.com
 
Posts: n/a

Default Re: Loading Cubes for SSAS - 09-26-2005 , 05:35 AM



jeje...

Yes I know you can do that but I don't want to "store" that level
either. I don't want the cube to be that large. So is there a way to
say to AS2K5 that in my fact table i have data that is productsku level
but in the cube I want to only "store" producttype level. Typically
what i'm doing right now is doing a groupby view of the fact and it
would be more elegant if I can just tell AS that here are my levels of
granularities of my cube that I want to store.

Thanks,
Rico


Reply With Quote
  #4  
Old   
Steven.Muise@gmail.com
 
Posts: n/a

Default Re: Loading Cubes for SSAS - 09-26-2005 , 12:36 PM



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


Reply With Quote
  #5  
Old   
ricocali@hotmail.com
 
Posts: n/a

Default Re: Loading Cubes for SSAS - 09-30-2005 , 09:25 AM



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:
Quote:
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


Reply With Quote
  #6  
Old   
Richard Kemp
 
Posts: n/a

Default Re: Loading Cubes for SSAS - 10-01-2005 , 11:21 AM



I think you could store the fact as an attribute on the dimension level
(i think its called attribute, i forget the terminology - and this is
from 2000 not 2005). Then use a calculated measure to pull the value
from the attribute. That make sense?

Another question is this product-level fact not a fact that can be
summarized through normal means of the fact table? Like a value that
you can't just sum/count/avg whatever?

- Rick

ricocali (AT) hotmail (DOT) com wrote:
Quote:
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



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.