Report hitting DQ instead of aggregated table only when cache is cleared and re-opening the report

[grangema]

Hello,

I created a report using Direct Query and Agregation tables. 

My data sources are BigQuery views.

Everything is working as expected : 

Data at the lowest level is hitting the Direct Query table

Data at a higher grain is hitting the aggregated tables.

On the main page, I only have information using one of my aggragated table.

But I noticed that if :

• I clear the cache :

• Close the report
• Open the report
• Use the performance analyzer
• Then the first thing my report is doing is sending direct queries to the source

• When the report is finally ready and my visuals correctly displayed, the direct query part is visible only in one of them :

• And if I now filter on a visual, then it's super fast and correctly using my aggregated table :

I only have this issue when clearing the cache and opening the report again, or when I publish the report on the service.

I don't know what to think about that. Is this the normal behavior for DQ ? Maybe it's sending a first request to the source to prepare the metadata ?

Thank you for your help,

[daxer-almighty · Accepted solution]

An aggregated table has to be created in memory from data that's gathered from the main system. Because most likely Microsoft thinks the aggregated data should be in sync with the lowest level data, PBI re-creates the aggregation in memory every time you clear the cache or open the file. I guess this is what happens. As long as your aggregations work after a refresh (which I think clearing cache or opening the file is) it's OK.