While working with OLAP we encountered weird results specially when working
with "averages" over 3 or more dimensions including Time dimension. Is the
order of dimensions creation in a cube affects the calculation order???

postyour question in the OLAP newsgroup
and explain what's appends and what you expect.

Show quoteHide quote

Nope, order of dimesion wont affect the average calculation. Your way of
looking into the average calulation might be creating the problem. Again in
your fact and dimesion design, if you have missed any suroggate key mapping
to dimension then it can waver your result.

i.e

Fact
-----
Product_id  Facility_id Time_id Measure1 Measure2
1                 1              1            20         20
1                 2              2           99          99
1                                2           1000       999

Here in this fact table(first three colum surrogate of dimesnion tables) we
are missing Facility_id in the 3rd row, so in aggregated value we miss third
row and our output value can waver.

We faced this issue once just thought to share!!!

This is bascially because, inside cube sql will form as inner joins between
fact and dimension....
Show quoteHide quote

Stop & Start SQL Server for using scm
expectations for SUM query on 50+ million rows
Internal SQL Server error
Move 2000 to 2005
Page coruption
Management Studio Question....
what kind of index to use in this situation.
Stored procedures in master database SQL Server 200/2005
how to crash/corrupt a Microsoft SQL 2005 Server?
deadlocked on lock