Wholesale and retail execution in composite models
HTML-код
- Опубликовано: 27 июл 2024
- In composite models, any query can be executed on the remote model (wholesale execution) or by mixing local and remote engines together (retail execution). This video describes the differences between the wholesale and retail modes in composite models.
Article and download: sql.bi/736550?aff=yt
How to learn DAX: www.sqlbi.com/guides/dax/?aff=yt
The definitive guide to DAX: www.sqlbi.com/books/the-defin... 
Наука
This is amazing, thank you so much, Alberto! :)
Thank you SQLBI, for both this video and such great content through the year. I really look forward to the upcoming content on composite models.
Thanks Alberto this is a long awaited feature that will hopefully come out of preview soon.
Really looking forward to more technical deep dives on composite models, in particular what we can do to manage performance.
Amazing intro. Thank you! Looking forward to future related videos.
Greay Vid Alberto Thanks!👍
Thank you, Alberto! 🙂
The question is can we consider the composite models optimized with aggregated tables as a strong rival against the premium models? i.e. Can we use composite models when our company can't afford the dedicated premium capacity for handling gigantic models?
Thank you again!!
Hi Alberto, thanks for all the videos. I have a situation where my dimension table itself has 495,000 records. How should I handle this type of database?
thank you
Hey Alberto, great video as always.
What about the calculated table used as dimension for the percentage. It is using a calculated column that is supposed to be generated on the fly when the query is sent to the wholesail dataset. And what about the calculated table, it is updated on at refresh time? Which means, if my wholesale model refreshes and have a new percetage value (that is not in my table) I'll get an integraty issue?
Calculated column on local tables and calculated tables are refreshed when you refresh the local model.
Calculated columns on remote table are evaluated at query time and are not materialized.
And yes its a big concern and irritating about power BI. Kindly Convence Microsoft Power BI developers to fix this issue. Thank you very much my dear friend Alberto Ferrari!!!!!
Alberto, can you please share with us how your UI for the creation and editing of visuals is so different from the vanilla version? Is this a new update or some add-in you have? Can you explain to us?
It is the preview of new format pane you can enable in Power BI Desktop December 2021:
powerbi.microsoft.com/it-it/blog/power-bi-december-2021-feature-summary/#post-18168-_Toc89785232
If coulumn is not store anywhere and will be computed every time we run a query then we don't have any benefits of Pre-Computed values.., Correct!?
Correct.
Hi there. I don't know what a Composite Model is?
This could be a good starting point: ruclips.net/video/9lkVk4t2qL0/видео.html
Im getting lazy with these videos. I don't want to read the article anymore 🙈
You miss many details if you miss the article!
@@SQLBI for sure... I think I'll start with the video and a week later go deeper reading the article.
Thank you for your work. Perfect as always.
Waiting for more content on the retail/wholesale chapter of calc groups!