I have followed the BOL steps to create a write-back enabled cube. Yet
when I run the Update MDX, it just times out and throughs an
out-of-memory error. It is a small cube and I am attempting to update
the leaf level. Can anyone confirm that the write-back feature works in
this release.

Steve

I can confirm that writeback works in this release. However, I suspect that
you are not doing it at the leaves level and you also probably use
EQUAL_ALLOCATION method instead of something like WEIGHTED_ALLOCATION.
To verify, you could try the following:

UPDATE CUBE Sales SET Leaves()(0) = 10

followed by

SELECT Leaves()(0) on 0 FROM Sales

This will guarantee that the update happens at leaves and not above.

--
==============================*=================== =
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebL*og/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==============================*=================== =
<Steven.Muise (AT) gmail (DOT) com> wrote

In my application, I need to enable my users to write back to levels
above the leaves for purposes of exploring different forecast scenarios
at more general levels than specific product. Is there a way to do
this?

Yes, of course it is possible. Simply based on the error that Steven
mentioned, I assumed that he wrote at too high level without proper
allocation, even though he assumed that he was writing on leaves.

--
==============================*=================== =
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebL*og/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==============================*=================== =

Are there cube design flaws/decisions that I could be guilty of that
adversely affect the writeback performance? I got it to work by
changing the ALLOCATION as you suggested. But it seems to take aweful
long time, and the cube isn't very large (couple thousand records in
the fact table). I can't seem to find any documentation about this.

Thanks

The fact that you got it working by changing allocation method proves that
you were not writing to the leaves. You need to review your UPDATE CUBE
statement to account for all attributes. If in doubt - you can use Leaves()
function for verification like I showed in the example in the previous post.

--
==============================*=================== =
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebL*og/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==============================*=================== =