Forum Discussion
Poorly performing DAX help
It turned out that having an intermediary table was causing the performancy issues.
A simplified version of my data model looks like this:
Date Dimension --- Page ---- Fundraising Page
Thankfully I was able to change the COUNTROWS to count the "Page" table not the "Fundraising Page" table - and by adding an extra filter, achieve almost the same result.
We guessed that maybe there was some kind of loop caused by the combination of the TOTALYTD and SAMEPERIODLASTYEAR functions (as well as the data model obviously) which meant that the performance was so slow.
Thanks for your help smoupre.
What do you mean by "need an aggregator around pages[page_status]"?
Yes, this is a column, and i'm only interested in rows from the related table which have a page_status not equal to 2.
Thanks again
Alex
OK, if it is a column, you don't need an aggregator like SUM, COUNT, etc. like you would in a measure.
If the table is related, perhaps use RELATEDTABLE or RELATED?
It turned out that having an intermediary table was causing the performancy issues.
A simplified version of my data model looks like this:
Date Dimension --- Page ---- Fundraising Page
Thankfully I was able to change the COUNTROWS to count the "Page" table not the "Fundraising Page" table - and by adding an extra filter, achieve almost the same result.
We guessed that maybe there was some kind of loop caused by the combination of the TOTALYTD and SAMEPERIODLASTYEAR functions (as well as the data model obviously) which meant that the performance was so slow.