Could it be that your nighttime update process is doing a full process of
one of the objects. This will clear out the log automatically.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"amosquera" <amosquera (AT) discussions (DOT) microsoft.com> wrote

You could set up your server to log the queries into sql server and before
you process your cube move the enteries into a history table and the process
your cube.

Of if you want to use ms access, you could suck the data out with a DTS job
and then process the cube.

Mark


"amosquera" <amosquera (AT) discussions (DOT) microsoft.com> wrote

Yes, you could do that so long as you are ABSOLUTELY sure that there are
structural changes. Remember that what the query log really contains is not
the queries themselves, but rather the aggregates that are requested as a
result of the queries. If things don't line up properly, the usage-based
optimization wizard could design ineffective or counterproductive
aggregates. That is why the system clears out the query log. It is to
protect you.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"mark hill" <mark (AT) mark-hill (DOT) com> wrote