![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
| You need to either optimize the joins away for the SKU and Category |
#3
| |||
| |||
|
|
This 2002 post provides 2 options, snowflake and unique level key, which work without need for custom rollups: http://groups.google.com/groups?q=di...snowflake&hl=e n&lr=&ie=UTF-8&oe=UTF-8&selm=3D6A3014.A0C9DB0D%40dsslab.com&rnum=2 You need to either optimize the joins away for the SKU and Category tables, or snowflake them so that SKU information is in a separate table from category information. (You could do both, too.) In order to optimize the joins, ensure that Category keys are unique within the level. Then, AS2K won't attempt to join in the product dimension when it processes the cube. The join is what throws off the numbers, as you get N fact rows per 1 dimension row. Your Forecasts will still have SKU disabled and join to Prod_catg_key in the category table (manually ensure this is set in the cube editor). You SKU information will join to SKU key. HTH .. - Deepak *** Sent via Developersdex http://www.developersdex.com *** Don't just participate in USENET...get rewarded for it! |
![]() |
| Thread Tools | |
| Display Modes | |
| |