Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have seen various articles and videos on how to create a new table that filters out the data from another table to give you a specific subset of the original table. I get the 'how' but I have not seen/heard any reason as to WHY. It seems that creating a new table of stored data unnecessarily increases the size of the data model and that could negatively affect performance. Why would I not just use one of the various methods of filtering data; slicers, the Filter pane, filter expressions in DAX, etc.? I think I mainly need a few examples/situations/use cases where this would be better or necessary.
Thank you.
Solved! Go to Solution.
One of the main goals in DAX Query optimization is the cardinality reduction. You balance the cost of additional storage with the benefits of smaller, more efficient queries.
Hi @WillBeeSEA
As highlighted by @lbendlin , the proposed approach appears to effectively address your requirements. Could you please confirm if your issue has been resolved?
If you are still facing any challenges, kindly provide further details, and we will be happy to assist you.
Best Regards,
Cheri Srikanth
One of the main goals in DAX Query optimization is the cardinality reduction. You balance the cost of additional storage with the benefits of smaller, more efficient queries.
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
63 | |
62 | |
52 | |
39 | |
24 |
User | Count |
---|---|
84 | |
57 | |
45 | |
43 | |
36 |