INCORRECT DATE WHEN USING MOLAP AND HOLAP STORAGE.

When designing storage for my OLap cubes . I notice that the data is not correct when using MOLAP and HOLAP storage , but is absolutely correct when I use ROLAP .

I have a total of 204 aggregations.If I process only 18 of those aggregations ,the data is correct on all MOLAP HOLAP and HOLAP cubes . but if I go above 18 only ROLAP retrurns the correct data. If the data is correct in ROLAP shouldnt it be the same in MOLAP and HOLAP as well ?

No the data must be the same. I think you have wrong something else.
Do you notice that data is double or greater?
Check partitions!!!
Try making only one partition first.
I hope it helps you.|||Well, the data is slightly different , I am using the following version of SQL

Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.0 (Build 2195: Service

,only one Partition was created and that is the one done by the system while processing the cube . I am unable to create any additional ones beacuse this is the Standard version and it does not permit user defined partitions (I need the enerprise version to do that ) Could it be a problem with the version ?

I wish I could show you, its the weirdest thing ever . The Rolap cube is Spot on , processed to a %100 performance . POLAP and HOLAP are out by a little by about 2 % less that the correct data.It seems to be filtering out some of the data.

My problem is , it is Slooooooooooooowww , and not practical considering I'm working with a database with Millions of Records.

HELLLLLPPPP !!!!|||Let me give you an advice. Never proccess a cube more than 30% of performance.
If you have a large cube (more than 2 o 3 millons of records) and 15 or 20 dimensions then 5% - 15% of performance it's ok.
In my last job I have a cube with 30 millons of records and I have partitioned it monthly without aggregations. And the performance was good.
If you can't make partitions then proccess cube without aggregations.
Validate the cube structure and optimize it.
Have you many virtual dimensions? They are not good for performance.
Tell me if it improve the performance.
|||

To tell the truth , the cube was not optimized , I'll do that and get back to you .
I have no virtual dimensions present .