Hello everyone,

I have very little OLAP knowledge and am trying to solve the following
mystery:

There is a data row that is not being included in OLAP reports. The
report runs off of a virtual cube made up of four actual cubes. Each of
the four actual cubes is split into yearly partitions.

In one of the actual cubes (we'll call it CUBE A), in the year 2006
partition there should be a row for a specific transaction. When
looking at the fact table behind CUBE A, the row exists. However, when
browsing the data for CUBE A, the data row cannot be found.

We have replicated the query in T-SQL, and the data row can be found.
We have done a full rebuild of all the shared dimensions for CUBE A,
and fully reprocessed CUBE A as well as the virtual cube it is in.

Could anyone throw out some possible reasons why the row that is
present in the fact table might not show up when browsing the cube
data?

Thanks in advance,

Jason

when you process a cube, AS2000 or SSAS2005 create a query with some joins
(regarding how the cube is optimize and other options)

So, process the cube using the management console and you'll see the real
query used by AS to load the data.
You'll certainly found a join which cause your row to disappear in the cube.

Its a common data quality issue, the row in the fact table use a key which
doesn't exists in the dimension.

Regarding which version AS you use, there is different options to insure the
loading of the cube, but I recommand to validate your data and verify that
the fact table contain only valid values.

<iaesun (AT) yahoo (DOT) com> wrote