dbTalk Databases Forums  

Accelerator for BI: Multivalued dimensions question

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


Discuss Accelerator for BI: Multivalued dimensions question in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Jim Reisz
 
Posts: n/a

Default Accelerator for BI: Multivalued dimensions question - 01-07-2004 , 09:52 AM






Does anyone know if Acclerator for BI has the capability to model
multivalued dimensions as explained by Ralph Kimball in
http://www.intelligententerprise.com...ouse1_2.shtml? For
Example, We can have up to 4 sales reps that can be assigned per sales order
line item. The fact table grain of our orders cube is the sales order line
item. Instead of creating surrogate keys in the fact table for Sales
Rep1..Sales Rep4 I have extended the application and created views as Ralph
explains in his article. I just thought I would ask to see if there is a
better way of handling this situation.

Thanks for your help.

Best Regards,
Jim Reisz



Reply With Quote
  #2  
Old   
Claudio Lucio
 
Posts: n/a

Default Re: Accelerator for BI: Multivalued dimensions question - 01-09-2004 , 05:59 AM






Hi Jim,
I had the same situation in a project with BI Accelerator. My advice: you
should forget to solve this problem with BI Accelerator.
Beyond of this, you could solve this using Analysis Services: Create
Another Cube (fact table in details)- 'Detail' Cube after this create your
Cube - 'Ordinary' Cube and you should use the Calculated Cells that do a
Lookupcube MDX function using the 'Detail' Cube.
If necessary i may send to you a example.




"Jim Reisz" <jreisz (AT) msn (DOT) com> wrote

Quote:
Does anyone know if Acclerator for BI has the capability to model
multivalued dimensions as explained by Ralph Kimball in
http://www.intelligententerprise.com...ouse1_2.shtml? For
Example, We can have up to 4 sales reps that can be assigned per sales
order
line item. The fact table grain of our orders cube is the sales order
line
item. Instead of creating surrogate keys in the fact table for Sales
Rep1..Sales Rep4 I have extended the application and created views as
Ralph
explains in his article. I just thought I would ask to see if there is a
better way of handling this situation.

Thanks for your help.

Best Regards,
Jim Reisz





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.