![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Howdy, can anyone direct me to an article, or make a resume here, regarding in which situations the Incremental update of dimensions doesn't work? I've come to the conclusion that if I change the hierarchy placement of a member in the dimension table, it gives error processing and it continues returning the same error even after changing the dimension table to its former state. Tore |
#3
| |||
| |||
|
|
Howdy, can anyone direct me to an article, or make a resume here, regarding in which situations the Incremental update of dimensions doesn't work? I've come to the conclusion that if I change the hierarchy placement of a member in the dimension table, it gives error processing and it continues returning the same error even after changing the dimension table to its former state. Tore |
#4
| |||
| |||
|
|
It depends on if the dimension is changing or not. 1) you can always add new members can be done via an incremental 2) a member can change its parent on an incremental of a changing dimension; a member cannot change its parent on an incremental process of a non-changing dimension. 3) member properties are always updated via an incremental -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Tore Johnsen" <naturamo (AT) hotmail (DOT) com> wrote in message news:e352OibwEHA.3448 (AT) TK2MSFTNGP10 (DOT) phx.gbl... Howdy, can anyone direct me to an article, or make a resume here, regarding in which situations the Incremental update of dimensions doesn't work? I've come to the conclusion that if I change the hierarchy placement of a member in the dimension table, it gives error processing and it continues returning the same error even after changing the dimension table to its former state. Tore |
#5
| |||
| |||
|
|
Thanks! That's the missing link i needed. Now, I'll have to define many of my dimensions as "Changing", but can anyone indicate if the lower query speed is notable at all? By what ratio will a query by say 1000 members be affected? Tore "Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> escreveu na mensagem news:OhJiWphwEHA.3528 (AT) tk2msftngp13 (DOT) phx.gbl... It depends on if the dimension is changing or not. 1) you can always add new members can be done via an incremental 2) a member can change its parent on an incremental of a changing dimension; a member cannot change its parent on an incremental process of a non-changing dimension. 3) member properties are always updated via an incremental -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Tore Johnsen" <naturamo (AT) hotmail (DOT) com> wrote in message news:e352OibwEHA.3448 (AT) TK2MSFTNGP10 (DOT) phx.gbl... Howdy, can anyone direct me to an article, or make a resume here, regarding in which situations the Incremental update of dimensions doesn't work? I've come to the conclusion that if I change the hierarchy placement of a member in the dimension table, it gives error processing and it continues returning the same error even after changing the dimension table to its former state. Tore |
![]() |
| Thread Tools | |
| Display Modes | |
| |