| Do not forget to set properly attribute relationship type (rigid or flexible). |
| Tuesday, 22 May 2007 16:54 | |||
|
Do not forget to properly set the attribute relationship type (rigid or flexible). If you can, use rigid. If the relationship is flexible and a change is detected during processing, all aggregates are dropped. You will need to add them back manually (using ProcessIndexes process type). You will not receive notice from the server that aggregations are dropped. After aggregations are dropped you might noticed slower performance of queries. - Vidas Matelis
|
Most read
- Process only one partition so you can browse the cube
- Create hierarchies in non-parent child dimensions
- Do not ignore duplicate key errors. Change the KeyDuplicate property of the error configuration ...
- Define a time dimension
- Do not forget to set properly attribute relationship type (rigid or flexible).
Top Rated
- Define a time dimension
- Do not ignore duplicate key errors. Change the KeyDuplicate property of the error configuration ...
- Avoid redundant attribute relationships because these relationships may prevent data from being ...
- Break distinct count measures into separate measure groups
- If you can, list in SELECT statement real measures first and calculated measures after
- Do not forget to set properly attribute relationship type (rigid or flexible).
- Process only one partition so you can browse the cube
- Remove aggregation designs that are not used by any partitions
Do not forget to set properly attribute relationship type (rigid or flexible). 
