Re: Analysis Services- Temp db overflow

#1 (**permalink**) 02-27-2008, 05:09 PM

"Lakshmanan" <babulaksh@rediffmail.com> wrote in message
news:03ba01c365d9$ff248d40$a601280a@phx.gbl...
> Hi
>
> We are using Analysis Services for OLAP , relational end
> being Sybase.
>
> In one of our cubes where the source table is huge in
> volume, we have a measure for which the aggregation type
> is "Distinct count" of a column in our fact.
>
> We have noticed that while processing the cube, since its
> a distinct count measure, analysis server builds a query
> with an order by clause on the distinct count source
> column.
>
> Since the table is huge and the query tries to
> order by , the temp db becomes full and the process gets
> killed.
>
> One of the reason for having it as a base measure over a
> calculated measure is the users want to drill through on
> it.
>
> Is there any way by which the above can be accomplished
> with out the temp db getting filled? Has anybody
> experienced it before?
>
> Any help will be appreciated.

1) Allocate a great space for temp.db

and/or

2) Isolate and build the distinct count out
of temp.db in a standard table.

#2 (**permalink**) 02-27-2008, 05:09 PM

Thanks a lot for all your suggestions.
I will try this out

Thank you again
Lakshmanan
>-----Original Message-----
>"Lakshmanan" <babulaksh@rediffmail.com> wrote in message
>news:03ba01c365d9$ff248d40$a601280a@phx.gbl...
>> Hi
>>
>> We are using Analysis Services for OLAP , relational
end
>> being Sybase.
>>
>> In one of our cubes where the source table is huge in
>> volume, we have a measure for which the aggregation
type
>> is "Distinct count" of a column in our fact.
>>
>> We have noticed that while processing the cube, since
its
>> a distinct count measure, analysis server builds a
query
>> with an order by clause on the distinct count source
>> column.
>>
>> Since the table is huge and the query tries to
>> order by , the temp db becomes full and the process
gets
>> killed.
>>
>> One of the reason for having it as a base measure over
a
>> calculated measure is the users want to drill through
on
>> it.
>>
>> Is there any way by which the above can be accomplished
>> with out the temp db getting filled? Has anybody
>> experienced it before?
>>
>> Any help will be appreciated.
>
>
>
>
>1) Allocate a great space for temp.db
>
>and/or
>
>2) Isolate and build the distinct count out
>of temp.db in a standard table.
>
>
>
>.
>

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode