Forcing SQL to use certain tables

[chael]

I am having an issue in 7.0.2 -- perhaps someone in this group has had this issue before. I have implemented some aggregate tables into my project but am having trouble forcing the reports to select from the tables. Mapping is set to automatic so all attributes and metrics can see the new table, I've updated the schema, and I have even manually adjusted the table logical size. I am in 2 tier so I have forced out caching as a source of my troubles.

Any suggestions?

 

[JRO061601]

It sounds like you may have simply overlooked some nuance in your report between the base fact table and the aggregate table, especially if there are multiple metrics. I would attempt troubleshooting by building the smallest report that you would expect to hit the aggregate table, and if it works, build it up one attribute/metric at a time. When it stops hitting the aggregate table, dig into the attribute/metric that tripped it up.

 

[chael]

JRO - you're right that there are things missing...one obvious area of concern is that all my base table joins are modeled correctly through corresponding attributes. So I have been careful to look at the model and analyze relationships, i.e. parent child, etc. There is simply one pass that is troublesome, because the 5 facts in that pass are modeled no differently than the 25 facts that go against the aggregate. Its a little frustrating, and requires digging. We'll figure it out in time, but sometimes when you hit a wall it doesn't hurt to throw it out to the community...

If anyone has any tricks, etc. that have worked in the past please advise.

Thanks,
Chael

 

[nlim]

something else to consider...for each of the 5 facts do a search for dependents and see if your aggregate table shows up. if they don't show up then dig into the fact definition to see if the aggregate tables are mapped.