<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16546" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=254492217-18102007><FONT face=Verdana
color=#000080 size=2>Can you clarify? Period and Period2 are based on the same
dimension table, with the same primary key, and the same foreign key from the
fact table? </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254492217-18102007><FONT face=Verdana
color=#000080 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254492217-18102007><FONT face=Verdana
color=#000080 size=2>At this point, it sounds like a bug in the aggregate table
recognizer algorithm. There may be a bug logged already. If you can convert into
a testcase on the foodmart schema that would help.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=254492217-18102007><FONT face=Verdana
color=#000080 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=254492217-18102007><FONT face=Verdana
color=#000080 size=2>Julian</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000080 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mondrian-bounces@pentaho.org
[mailto:mondrian-bounces@pentaho.org] <B>On Behalf Of </B>Ati
Rosselet<BR><B>Sent:</B> Thursday, October 18, 2007 2:58 AM<BR><B>To:</B>
mondrian@pentaho.org<BR><B>Subject:</B> [Mondrian] Problem with aggregate
tables..<BR></FONT><BR></DIV>
<DIV></DIV>Hi, I'll try to be clear here. <BR>We are running mondrian
2.4 with the Aggregate query generation turned on at the moment and we have
the following, odd situation:<BR><BR>We have 2 dimensions (Period and
Period2), both of which reference the same set of id's <BR>We have also
created the appropriate aggregate table for a certain level, and all works
fine.. kind of.<BR><BR>The problem is that when the query using "Period" runs,
the aggregate table we created is shown on the console, and the database logs
show that it used, and consequently everything is FAST!! However, when
using the "Period2" dimension, although the EXACT SAME table is shown on the
console as a suggested aggregate table.. it is never used. <BR><BR>I
could understand if it was finding a 'better' table and using that instead,
but rather it is not using any aggregate table at all.
??????<BR><BR>What situation could cause the processing of an MDX query to
list "suggested" tables, and then NOT use one of them if it exists? <BR>We've
been trying, tweaking etc.. and no change.. at a complete loss
here... any ideas?<BR><BR>Cheers<BR>Ati<BR><BR><BR>(Julian... just found the
new mailing list - thnx... did you shut down the old spamful one?)
<BR></BLOCKQUOTE></BODY></HTML>