Hi all,
I have a cube with a number of partitions in a measure group based on a monthly 'run key'. I have the correct slicer set
I modify one of the dimension attributes for a single dim row that I know only exists in one partition. The attribute's relationship to the dim key is flexible and it is not part of any user defined hierarchy
But when I process the dim and check 'process affected objects' (so it rebuilds the aggregations), it appears to touch every partition in my measure group.
Yes it completes much faster than a full process of the measure group, but still... Can I do anything to avoid it? Are there better ways to do this using xmla that will not touch unrelated partitions?
Thanks
Jakub @ Adelaide, Australia