Re: Optimizing this very slow query
- From: "Jéjé" <willgart@xxxxxxxxxxxxxxxxx>
- Date: Wed, 6 Apr 2005 21:38:45 -0400
executing the query at the server side will use 100% of the server CPU
instead-of 100% of the client CPU.
Because, by default, the client evaluate the formula, so 100% of the
client's cpu is used.
you can improove the performance by setting up the right aggregations in the
cube, I mean insure that the levels used in your queries are aggregated.
what your query do?
you want to display values only for monthtime with source & destination
available?
"Charlie" <charlie> wrote in message
news:eKYbu%23nOFHA.2384@xxxxxxxxxxxxxxxxxxxxxxx
> Thanks for that read. The problem is not the bandwidth or the sending of
> the data. So I don't know how much of a speed difference it will make
> asking for server execution. Besides I tried that connection string change
> yesterday and it seemed to produce an unstable connection (the application
> reported all sorts of strange errors fetching dimension data).
>
> I believe the problem is in the way the client applies the where
> condition. See the thread "Why is this query faster?" in this group for
> the question this has led me to.
>
> Thanks,
> Charlie
>
.
- References:
- Optimizing this very slow query
- From: Charlie
- Re: Optimizing this very slow query
- From: Jéjé
- Re: Optimizing this very slow query
- From: Charlie
- Optimizing this very slow query
- Prev by Date: Re: Reporting Services Charts...
- Next by Date: Re: MDX function does not working with multiple selection in OWC
- Previous by thread: Re: Optimizing this very slow query
- Next by thread: use DSO to Merge partition error when open with Analysisi Mananger
- Index(es):
Relevant Pages
|
