This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hi all,
I've been doing some light reading on columnar storage and the Vertipaq engine (here). It made me wonder if it's better practice to apply multiple conditions in the filter pane, or create columns in Power Query such as [Within_12_Months_andor_Other_Conditions] that return a boolean result and filter on that? The chapter linked indicates Vertipaq is fastest when working on only a small number of columns.
And to expand on that, if there were multiple such columns, could any efficiency come from putting them in a separate related table (star schema)?
Solved! Go to Solution.
Hi , @Anonymous
When working with Power BI, it is generally better to apply multiple conditions in the filter pane rather than creating columns in Power Query such as [Within_12_Months_andor_Other_Conditions] that return a boolean result and filter on that. This is because the filter pane is optimized for filtering data and is faster than creating additional columns.
Regarding your second question, creating a separate related table (star schema) for multiple such columns can improve efficiency. This is because star schema is optimized for querying and aggregating data, and can improve query performance.
However, it is important to note that the efficiency of star schema depends on the size and complexity of the data. For small datasets, the performance gain may not be significant enough to justify the additional complexity of creating a star schema.
Thank you for your time and sharing, and thank you for your support and understanding of PowerBI!
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Hi , @Anonymous
When working with Power BI, it is generally better to apply multiple conditions in the filter pane rather than creating columns in Power Query such as [Within_12_Months_andor_Other_Conditions] that return a boolean result and filter on that. This is because the filter pane is optimized for filtering data and is faster than creating additional columns.
Regarding your second question, creating a separate related table (star schema) for multiple such columns can improve efficiency. This is because star schema is optimized for querying and aggregating data, and can improve query performance.
However, it is important to note that the efficiency of star schema depends on the size and complexity of the data. For small datasets, the performance gain may not be significant enough to justify the additional complexity of creating a star schema.
Thank you for your time and sharing, and thank you for your support and understanding of PowerBI!
Best Regards,
Aniya Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly
Hi Aniya,
Thanks for your reply. Looks like it is worth sticking to measures instead. Cheers!
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 33 | |
| 26 | |
| 21 | |
| 20 | |
| 15 |
| User | Count |
|---|---|
| 63 | |
| 44 | |
| 28 | |
| 24 | |
| 22 |