If you need to use a specific table , we need to play with the logical size of that table. Whenever MSTR frames a query it retrieves data from the table that has the least logical size and hence when you set the logical size of your table to be least compared to the other base table, MSTR will retrieve data from this specified table.

Hope this helps

Thanks,

SaiGanesh

I would use level metrics to force the SQL generation (remove the report level from the metric and add level on ALL the dimensions from the fact table you want to generate SQL against).  By doing this you will only affect the report that is using the metric.  If you start altering the logical table size you will affect all reports.

I would use level metrics to force the SQL generation.

• Remove the Report Level from the metric(s)
• Add Leveling to the metric(s) for each of the Deminsions/Attributes in the Fact Table you are trying to force in the SQL

By doing this you will only affect the report that is using the metric.  If you start altering the Logical Table Size, you will affect other reports.