Hello!
I have a cube with 68 dimensions and 12 measures.
When a try to use usage-based optimization it doesn't dislay any
result querys.
trying to solve this problem i realise that if i use only 64 dimension
the usage-based optimization works! I had use molap and holap sotage.
My server as SP3a to AS. Is there any way to increase this limit?
Someone now how to solve this problem?

Another question, why aggregations made with this tool only woks after
the cube was full processed? Why doesn't work if i use incremental
update?

Thanks in advanced

André Fonseca

Hi Andre,

This issue reveals an inconsistency between the documented max number of
dimensions in a cube (128) and the maximum number of characters that can be
stored in the query log (64) for the Dataset and Slice fields.

Editing the design of the QueryLog table and setting the Field Size
property of the Dataset and Slice fields to be 128 instead of 64 resolves
this problem.

For your other question when you create new aggregations should they be
completly filled with all data not only the new data (incremented). That's
whey you need to do a full process.

HTH,
Bas

"This posting is provided "AS IS" with no warranties, and confers no
rights."

Thanks for everything!!!

André Fonseca
botinha (AT) netcabo (DOT) pt (Botinha) wrote in message news:<9587965.0404080214.1fe18760 (AT) posting (DOT) google.com>...