I'm trying to do some benchmarking tests on Analysis Server, so I'm
trying to make sure that I'm not getting any caching effects. I've
been reading that issuing a REFRESH CUBE [cubename] should clear the
client side cache, but it doesn't seem to be happening for me. If I
issue a query, I see it show up in the Analysis Server log
(msmdqlog.mdb). If I then issue a REFRESH CUBE statement and then
send the same query (all using the same open connection that was used
for the first query), I don't see it show up in the log (presumably
because it was caught by the pts cache). Does anyone see something
obvious that I'm doing wrong here?

REFRESH CUBE cleans the client cache, but not the server cache - that's why
you see no updates in the Query Log. In order to clean server cache - issue

Process processSuspend
Process processResume

from the DSO application on the applicable object.

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================
"David Hwang" <davidhwang (AT) usa (DOT) com> wrote

Thanks for clearing that up. Is there any other way that I can verify
that the query actually hit the server? For my performance testing,
it's fine if the server cache is used, I just need to make sure that
the queries actually make it to the server. Basically, right now I
can't tell if the client cache is really getting cleared or not.

"Mosha Pasumansky [MS]" <moshap (AT) online (DOT) microsoft.com> wrote

Also, I noticed that if I send the same query 100 times but use
different connection objects, then I see 100 entries in the query log.
But shouldn't the server cache be catching those queries also? In
the query log, I notice that only the first entry has a "1" for
MOLAPpartition, the others have a "0". I had assumed that that meant
that all queries after the first were hitting the server cache.

"Mosha Pasumansky [MS]" <moshap (AT) online (DOT) microsoft.com> wrote

You are right - the MOLAPPartitions column shows how many MOLAP partitions
were hit by that query. 0 means that they were all answered entirely from
the cache.

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

Does that mean that the REFRESH CUBE statement isn't working for me
since it seems like those queries aren't even hitting the server
cache?

"Mosha Pasumansky [MS]" <moshap (AT) online (DOT) microsoft.com> wrote

Did you set query log sampling frequency to 1 ?

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

Yes, I managed to figure that out after a bit of confusion.

I was wondering if either the server cache or the log was doing
something connection specific that might explain this behavior that
I'm seeing.

"Mosha Pasumansky [MS]" <moshap (AT) online (DOT) microsoft.com> wrote