|
Home > Archive > MS SQL Server OLAP > January 2006 > Processing of Dimensions in Analysis Server stuck
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Processing of Dimensions in Analysis Server stuck
|
|
| nojetlag 2006-01-26, 4:58 pm |
| Hi there,
I ran into an issue where Analysis Server gets stuck in processing
Dimensions. I have 3 Cubes and both ways (via processing only the
dimensions or as a full process) the processing gets stuck. What makes
me frustrated is that there is plenty of RAM still available.
It always happens around the same spot, just after processing a
dimension with around 800'000 rows. The next dimensions are just stuck
and after an iceage time it is processed, even though they only have
around 6-10 rows. Before that the processing runs smooth and fast.
I have the same on production environment and there it works, however
on the development machine I hit this problem. The CPU load goes at the
same time down to < 5%.
Any body having a hammer to hit this beast ?
best regards
andreas
| |
| Denny Lee 2006-01-26, 4:58 pm |
| I take it this this is occuring on Analysis Services 2000 - out of
curiosity, are you processing the dimensions individually or are you
processing them all at once (open up Analysis Manager, right-click
dimensions, and click on "Process Dimensions"). As well, are there any
errors within the event log that are occuring at the same time (e.g. lazy
aggregation error, out of memory, etc.)
--
HTH!
Denny Lee
< dennyglee_at_hotmail
_dot_com>
Blog at:: http://spaces.msn.com/members/denster/
"nojetlag" <apa57@hotmail.com> wrote in message
news:1138293321.412308.210290@g14g2000cwa.googlegroups.com...
> Hi there,
>
> I ran into an issue where Analysis Server gets stuck in processing
> Dimensions. I have 3 Cubes and both ways (via processing only the
> dimensions or as a full process) the processing gets stuck. What makes
> me frustrated is that there is plenty of RAM still available.
> It always happens around the same spot, just after processing a
> dimension with around 800'000 rows. The next dimensions are just stuck
> and after an iceage time it is processed, even though they only have
> around 6-10 rows. Before that the processing runs smooth and fast.
> I have the same on production environment and there it works, however
> on the development machine I hit this problem. The CPU load goes at the
> same time down to < 5%.
> Any body having a hammer to hit this beast ?
>
>
> best regards
> andreas
>
|
|
|
|
|