Hi experts, I am trying to improve performance in one of our cubes by building aggregates.
This cube contains only records with transaction types A and B. When I use RSRT and the debug option "Display Aggregate Found" I notice that several queries make one call on this cube with a static filter on transaction type Z, which will never exist in this cube.
My scope is not to change queries, so I have no intention of investigating why the queries make this call. What I would like to do is just to build aggregates to speed up the queries.
First I built an aggregate containing all the characteristics of the cube, but with a static filter on transaction type Z, meaning this aggregate always had 0 records. Whenever using these queries, this aggregate gets hit, so it seems to work as I wanted it to.
My question is if it actually gives any performance gain? Since transaction type Z does not even exist as a key in the cube's dimension table, maybe it would be more or less as fast to query the cube directly? I am not sure of how the query asks for information, but I guess that if it cannot find a key in the dimension table, it will never even have to search the fact table?
Thanks in advance for your help!
Martin