Какие действия приведут SSAS куб в состояние unprocessed.

http://bimic.blogspot.com/2011/08/ssas-which-change-makes-cubedimension.html

Which change makes the cube/dimension unprocessed?

In many cases, some of OLAP cubes are huge and Full Process takes a lot of time.

Therefore, it’s important to know which change, when the updated solution is deployed, causes the cube to move to “Unprocessed” status and needs new full process. Dimension process status is also critical since if dimension moves to unprocessed, all cubes that have connection to this dimension will be unprocessed too.

Here is the detailed tested list of different actions, and how they apply on cube (tested on SSAS 2008. I don’t remember any difference with

SSAS 2005, but not certified)

We can summarize the results in one sentence: Every action that affects

data

will move cube or dimension status to unprocessed. Such changes are also called structural changes, meaning any change that apply on cube/dimension structure (new element, edition on aggregation method, etc.) and therefore will require data loading or reloading.

One exception

: Adding or deleting translation to dimension unprocesses it when deployed. I don’t know why..

And now to the detailed list: