I've seen a couple of posts on this but not a real good answer as to what is
happening.

If I:
1. delete data from DW
2. rerun ETL to load DW
3. then reprocess cube
---- I get OLAP storage error

If I:
1. delete data from DW
2. rerun ETL to load DW
3. reprocess each Dim individually
4. then reprocess cube
--- it works

Any idea what causes this? Am I missing a patch for SQL? Originally this
did not happen until I added another Fact table and created a second cube.
At some point I had to pull that Fact table out and reprocess what I had.
I've had the error ever since.

As you know, data from dimension table and Members from dimension structure
must be matched.
If you guarantee this, you can skip dimension processing.

Of course, the reference consistency between dimension tables and fact table
must be kept.
If not, it will cause key errors.

I think you should check what are really changed after delete and reload DW.

Ohjoo

"DuaneS" <DuaneS (AT) discussions (DOT) microsoft.com> wrote

your dimensions changes, so if you do a standard process, AS will update the
dimensions and if there is an issue (Ilike a rigid relationship relation
changes) then you'll receive errors.

this is a standard case when some members move in a dimension.
Like the city change from province A to B during 2 different DW loading.
you must do a full process of the dimension when this case occurs.

or you can change the relationship from rigid to flexible (in SSAS2005) to
not receive this error again. but this cause the dimension and cubes to be
slower.

I recommand to take a closer look at the error to idnetify which dimension
is in error and correct the source data to insure that the members don't
move again (if its applicable)

I hope this will helps you.


"DuaneS" <DuaneS (AT) discussions (DOT) microsoft.com> wrote