Please explain the logic in last measure, I didn't get it. You are just trying to add results of two calculate functions instead of applying condition.
In the last example it shows that, if we use such conditions inside the iterator function like SUMX() over a large fact table, it will be slow. because it is going to validate over each row for those conditions. at the otherhand. calculate works on modified filter context. so it will first apply those filters, and then will calculate. which will be more efficient as compare to previous.
But the Replaced DAX functions are blazing Fast. Is'nt it?🙂 The Key takeaway is, there are multiple ways to get a particular result, but what is the most optimized way which improves the performance of the overall DAX query.
This is a great topic, thanks for sharing!
You are so welcome!
great learning , thanks
Glad you liked it!
Please explain the logic in last measure, I didn't get it. You are just trying to add results of two calculate functions instead of applying condition.
In the last example it shows that, if we use such conditions inside the iterator function like SUMX() over a large fact table, it will be slow. because it is going to validate over each row for those conditions. at the otherhand. calculate works on modified filter context. so it will first apply those filters, and then will calculate. which will be more efficient as compare to previous.
This video is very slow and monotone in delivery - What are the key takeaways?
But the Replaced DAX functions are blazing Fast. Is'nt it?🙂
The Key takeaway is, there are multiple ways to get a particular result, but what is the most optimized way which improves the performance of the overall DAX query.
ai voice is putting me to sleep
Horrible