cube totals don't match the database

[Kasima]

Hi!

I have a cube with 26 partitions. All of my partitions match the database in all measures, except for one anomaly. I have 1 partition that has 1 measure that does not match the database. I have tried reprocessing it as well as recreating the partition. I have recreated the entire cube, but that partition still doesn't match. I have also created a cube with just that partition with just that measure, and that one matches the database.

The discrepancy is not large, possibly rounding. But, I find it strange that I'm not experiencing these problems in any other partitions.

I even went in and changed the storage options to store 100% of the aggregations just to see if that would help. After processing that partition for 5 hours, it still had the wrong total. It was the same wrong total though so at least it's consistent!

Does anyone have any ideas? Do I just need to live with it? I've never had problems with analysis services cubes not matching the database so I'm baffled. It doesn't inspire confidence.

Thanks,
Kasi

 

[justins57]

Kasi,

How are you partitioning the Cube, by Time or some other dimension? When you rebuild the Partition can you review the SQL it is using, maybe that will help answer your question.

Justin

 

[DWArchitect]

Hi,
Yes, I have similar problems with my totals changing when I added new dimensions.

I believe it is because a fact table foreign key is not found in the dimension table so that row is not counted or processed.

Sometimes I get a changing number of rows processed after I add a new dimension. I was wondering if it was due to referential integrity regarding missing or duplicate key values.

DW Architect