September 8, 2008 at 8:00 am
Hi,
we've got a cube with partitions containing one year's data each. We'd like to load just the most recent partition from our database. We can't identify additional rows. Therefore we can not just processUpdate the partition. We always have to load it completely.
I've set up a SSIS package for this workflow. I've started with just one analysis service processing task (I hope the translation is correct, I've got a german system in front of me). Here I selected to fullProcess the partition for 2008 and all dimensions. With the result, that the cube could not be accessed afterwards. Than I've changed it to fullProcess the partition and to processUpdate the dimensions. The result does not realy look any better. Next I've splitted the prcessing into one component for processing the measure groups and one for processing the dimensions. It does not matter in which sequence or with what processing option I've processed the components the result was, that the additional data where not shown in my cube.
What's wrong? How can I automize fully loading of just one partition without touching the others?
Kindest,
Ralf
September 8, 2008 at 8:07 am
Do a "Process Update" on any related dimensions that have had data changes.
Do a "Process Data" on the individual partition for the measure group you have added data to.
Do a "Process Index" or "Process Default" for the entire cube to re-create any dropped indexes due to the processing.
September 9, 2008 at 1:04 am
Hi Michael,
thanx for the information. I've just tried in exactly the same order without success. I've still got just the old data from the cube. Do you've got any idea?
Kindest,
Ralf
September 9, 2008 at 4:33 am
I have to assume you have something directed to the wrong table, a bad join, or something else preventing the cube from getting your new data.
September 9, 2008 at 4:40 am
Don't think so. Full processing of everything does exactly what I want. Only partial processing does not work.
September 10, 2008 at 3:01 am
Hi Michael,
you've been right. We've had a bug in the sql statement. I've fixed it an will try to partially load tomorrow.
Thanx for you help!
Kindest,
Ralf
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply