This may be just a trivial issue.
I have a sales fact table with 4 seperate dimensiontables.
My Sales Cube draws from all 4 dimensiontables.
When processing the cube I reckon the first step is the execution of the SQL (by inner joins) to create the complete dataset.
With new fact data I keep running into processing errors with remarks about members no existing in a dimension table (and existing in the facttable)
I would expect that this is dealt with by the inner joins in the process SQL?
When rebuilding the shared dimensions the problem is solved.
Can I avoid this by defining the dimensions as 'changing' dimensions?
Ties Blom
Information analyst
I have a sales fact table with 4 seperate dimensiontables.
My Sales Cube draws from all 4 dimensiontables.
When processing the cube I reckon the first step is the execution of the SQL (by inner joins) to create the complete dataset.
With new fact data I keep running into processing errors with remarks about members no existing in a dimension table (and existing in the facttable)
I would expect that this is dealt with by the inner joins in the process SQL?
When rebuilding the shared dimensions the problem is solved.
Can I avoid this by defining the dimensions as 'changing' dimensions?
Ties Blom
Information analyst