Can anyone explain what the DQM Summary Query setting does, or point me to an example please?
The documentation is a bit light...

"You can retrieve summarized data without entering explicit aggregates in expressions in query items by
specifying a query subject in an IBM Cognos Framework Manager model to be a summary query.
You can add query items that are already summarized from the summary query into your reports that you
create in IBM Cognos Analytics. You do not have to repeat complex formulas or calculations in each report
that you create."

I understand that this creates a 'summary' sql statement, for example, turning this:

into this:  

but wonder in what scenario this is better. is it purely about a filter being a detail vs aggregate filter?

------------------------------
Marc Reed
------------------------------

Hello Marc,

This option is mostly useful if there is actual aggregation taking place. Mostly used when you define a view over other tables or views and project viewer grouping columns than the groupable columns of the source tables or views.
In you example, if you had a view over the page_4 table, but removed the projections/fields Product_type, Product then it is likely that there is aggregation taking place, in which case it might be helpful. If the database that you're dealing with has aggregate table rewrite, then this option may in some cases make matching against an existing aggregate table more successful.
Hopefully this helps (a bit)

Per Henk and docs.
https://www.ibm.com/docs/en/cognos-analytics/12.0.0?topic=mode-creating-summary-query-in-model

As you may recollect, persons might define a query subject in FM, go to test it thinking they'd see a grouped-query as in RS.
Which is why the auto-summary check box is there in FM.

While some folks write explicit aggregating expressions in a model (total ( x ) ...) etc. Some might ask how they might avoid that.

Last, should you have any concerns about filtering, it will become a function of when might the filter be pushed (applied) pre-grouping/aggregation vs post in an engine.  For example filtering on the grouping (categories) vs filtering on an aggregated value etc.