Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hello all,
This is more of a 'best practice' question. I have a web based excel file (24 columns, 250 rows) in which I hosts my data. From this, I've used Power BI Desktop to create multiple calculated columns, measures, and calcuilated tables.
Im seeing that the visual refresh times are slowing down substantially, so I'm interested in knowing from the Experts... What's best... a pages of visuals using multiple calculated measures, calculated columns, or should I try to condense this into a much smaller summarized New Table with calculated columns?
Thanks everyone!
Solved! Go to Solution.
I think most people will say it depends. Your data structure, what you're using the calculated column or measure for, how static/dynamic they can be... several things play into it, and it's hard to know exactly what you need from what you've mentioned. For calculated column vs measures pointers, I recommend checking what some of the experts have already written. A couple of good examples are on PowerPivotPro and ExceleratorBI.
As far as calculated tables, are you talking about creating tables from scratch, like a calendar table? If you're moving to a condensed table, it sounds like you could just remove several of the rows while you're in the query editor before loading to the model. Any time you can reduce your table size in rows or columns, you'll help your performance to some degree.
I think most people will say it depends. Your data structure, what you're using the calculated column or measure for, how static/dynamic they can be... several things play into it, and it's hard to know exactly what you need from what you've mentioned. For calculated column vs measures pointers, I recommend checking what some of the experts have already written. A couple of good examples are on PowerPivotPro and ExceleratorBI.
As far as calculated tables, are you talking about creating tables from scratch, like a calendar table? If you're moving to a condensed table, it sounds like you could just remove several of the rows while you're in the query editor before loading to the model. Any time you can reduce your table size in rows or columns, you'll help your performance to some degree.
User | Count |
---|---|
140 | |
113 | |
104 | |
77 | |
65 |
User | Count |
---|---|
135 | |
117 | |
101 | |
71 | |
61 |