|
Home > Archive > MS SQL Server OLAP > March 2006 > Any limits to dimension size in AS 2000?
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 |
Any limits to dimension size in AS 2000?
|
|
| Kaisa M. Lindahl Lervik 2006-03-30, 7:32 am |
| I have an OLAP database consisting of 3 cubes, 2 regular and 1 virtual.
If I do a clean process of this cube, everything runs OK. If I try to
reprocess it, it starts, and just continues running without doning anything
usefull. I don't think it's a memory issue, as it never stops hanging, like
it usually does if there's a problem with memory.
The developer says that he's seen this behavior before, that reprocessing
hangs if the dimension size is too big, but he hasn't found any
documentation on that. So my question is: Is there a limit? Is it
documented? If documented, where can I find it?
So far, our work around has been to just run a script that will Stop the
OLAP service, delete the data files (not really necessary, but cleaner),
start the OLAP service and then run full process. But this solution works
only for those "in the know", so if any other persons want to do the
processing, it just hangs. I want to find a more stable solution to the
whole problem. Any suggestions?
All help appreciated!
Kaisa M Lindahl Lervik
| |
| necati@cbksoft 2006-03-30, 7:32 am |
| I think in AS 2000, the maximum number of dimensions is 128. I dont think
your problem is about that.
While updating, if there are new members for any dimension (For example, a
new year in salesDate dimension) it will possibly cause errors. If you
process the dimensions first and then just try to process the cube this
problem may be solved.
--
Necati Sekkeli
CBKSoft
Junior Software Developer
"Kaisa M. Lindahl Lervik" wrote:
> I have an OLAP database consisting of 3 cubes, 2 regular and 1 virtual.
> If I do a clean process of this cube, everything runs OK. If I try to
> reprocess it, it starts, and just continues running without doning anything
> usefull. I don't think it's a memory issue, as it never stops hanging, like
> it usually does if there's a problem with memory.
>
> The developer says that he's seen this behavior before, that reprocessing
> hangs if the dimension size is too big, but he hasn't found any
> documentation on that. So my question is: Is there a limit? Is it
> documented? If documented, where can I find it?
>
> So far, our work around has been to just run a script that will Stop the
> OLAP service, delete the data files (not really necessary, but cleaner),
> start the OLAP service and then run full process. But this solution works
> only for those "in the know", so if any other persons want to do the
> processing, it just hangs. I want to find a more stable solution to the
> whole problem. Any suggestions?
>
> All help appreciated!
>
> Kaisa M Lindahl Lervik
>
>
>
|
|
|
|
|