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 - Need some tips/advice on the model I am working on. Its pretty complex with a lot tables and some of my fact tables have 20 million +rows. When creating my visualizations, is it better (performance wise) to filter on fields in my Fact tables or is better to create dimension tables (would only be one column) and filter off that? For example, I have to filter on one field "FieldName" in one of my fact tables that has about 100 different options. Would it better to create a dimension table with those 100 different options, link it to my fact table, and filter off the dimension table instead?
Hi @PowerBI123456 ,
Continue to create dimension tables will make the data set larger, which in turn will slow down refreshes and queries.
Try to refer to the link.
Data reduction techniques for Import modeling
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Yes, it should improve the performance... try it and see.
I would create a dynamic table based off your fact table, create a New Table, = distinct(FactTable[columnName]). Then create the relationship with the FactTable.
Also, use the "Performance Analyzer" under View menu to test the performance.
Check out the May 2026 Power BI update to learn about new features.
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 |
|---|---|
| 32 | |
| 25 | |
| 23 | |
| 22 | |
| 13 |
| User | Count |
|---|---|
| 61 | |
| 47 | |
| 27 | |
| 24 | |
| 19 |