Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
hi
the case is as follows:
- I have the facts that are binary in nature but aren't to be aggregated directly (due to business rules, as they are the same in granularity but different in interpretation) and in DAX they need to be put as not a very complex, but still robust set of CALCULATE modifiers (several direct filters + some summing of columns, maybe even using iterator with RELATED sometimes)
so I have two options:
1) go with a classic CALCULATE( aggregation, modifier1, modifier2, ... )
2) or to generate flag columns during import, that will reduce the DAX from the above example into SUM(single column) - or worst case scenario CALCULATE( aggregation, flag = something)
I expect to generate a set of up to 5 flag columns with 0/1/NULL
I estimate the fact table to grow into 100 million rows within a year
what will be a better performing option here using Direct Query mode?
it possible to generate those flags at the source?
For example, through a SQL view?
I believe that would be the best performance option.
yes, that's the only option we are taking into consideration
either normal model with more complicated measures
or additional flag columns in an SQL query during import
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Ask questions in Eventhouse and KQL, Eventstream, and Reflex.
User | Count |
---|---|
88 | |
82 | |
65 | |
64 | |
58 |
User | Count |
---|---|
171 | |
113 | |
110 | |
73 | |
73 |