The book, or Bible, The Definitive Guide to DAX, was paramount for me in understanding SE and FE. Your teaching style is amazing. I hope to one day thank you both personally.
@@marcorusso7472 Sure. If we want to see the calls (whether SE query request to FE Or FE requesting SE ), is logical query plan better or physical query plan ? In short, which query plan shows us all the requests/calls from SE/FE to FE/SE ?
In general, is a welcome improvement. As always in almost all of the optimizations, there are corner cases where the impact could be null or negative, but in the majority of scenarios it provides a performance benefit, mainly for DirectQuery, but also for VertiPaq in particular cases.
The book, or Bible, The Definitive Guide to DAX, was paramount for me in understanding SE and FE. Your teaching style is amazing. I hope to one day thank you both personally.
Good explanation (as always), thank you!
Marco! Not using DAX Studio 3 in the demo!?
I’m sure this video was recorded before this version. ;)
True, it was recorded before the release of DAX Studio 3!!
Excellent!
Q: Which query plan to be best referred, to identify the calls from FE to SE and vice versa (CallBack) ?
I don't understand the question, can you clarify please?
@@marcorusso7472 Sure. If we want to see the calls (whether SE query request to FE Or FE requesting SE ), is logical query plan better or physical query plan ?
In short, which query plan shows us all the requests/calls from SE/FE to FE/SE ?
Great work Marco! I’m curious, what is your opinion regarding Horizontal Fusion for Power BI as recently announced by Microsoft?
In general, is a welcome improvement. As always in almost all of the optimizations, there are corner cases where the impact could be null or negative, but in the majority of scenarios it provides a performance benefit, mainly for DirectQuery, but also for VertiPaq in particular cases.