Forum Discussion

Svet_Dimov's avatar
Svet_Dimov
Frequent Visitor
2 years ago

Design question fact table rows vs columns

I have a question regarding what would be a more optimal design of a directquery fact table. Currently I have a table in the following format: timestamp dimension dimension_A_value (Null for all ...
Need Help
Svet_Dimov's avatar
Svet_Dimov
Frequent Visitor
2 years ago

Thanks a lot for the response, Greg_Deckler! My main concern is that  I would be adding a CALCULATE function to the DAX and I am not sure if it has a performance Impact on the DirectQuery.

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    Hi Svet_Dimov ,Greg_Deckler, thank you for your prompt reply!


    The short answer is Yes, quoted from the official documentation:

     

    At least initially, it's recommended to limit measures to simple aggregates.

     

    The aggregate functions include SUM, COUNT, MIN, MAX, and AVERAGE.

     

    Then, if the measures are sufficiently responsive, you can experiment with more complex measures, but paying attention to the performance for each.

     

    While the Calculate DAX function can be used to produce sophisticated measure expressions that manipulate filter context, they can generate expensive native queries that don't perform well.

     

    Best regards,

    Joyce

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.