Re: Millions of rows, storing aggregate/rollup results help please

[Rick James]

Another way to tackle a problem like this is to keep a log of what queries users ask for. Then review them -- you will probably find that a couple of filters are almost always included. Build combinations that include common patterns, and let the other combinations be more costly. (Your app code would need to understand to either reach for a summary table (fast) or reach for the Fact table (slow).)

If you would like to present such a log, I will make a stab at what combos to make.

I see no provision for counting NULLs; is there such? If not, then maybe (let's say) Filter8 shows up only these three ways:

AND Filter8 = 0
AND Filter8 = 1
# Filter8 not specified, hence (0,1,NULL), which cannot be done with IN(...).

Or do you also have
AND Filter8 IN (0,1) -- same as Filter8 IS NOT NULL?