Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi. I have a table that has millions of rows of user activity on accounts and the table has an index column which helps me determine the chronologically of specific activities in my measures. However, the performance is sucky because the size of the table. Are there any best practices on how to deal with that? Unfortuantely, I can't show any of the data because its confidential, but just wanted to see any general best practices. Thanks!
Solved! Go to Solution.
Depends on what you are doing
Check these for reference
Speed/Performance aspects – The BIccountant
Watch Your Steps! Power Query Performance Caution for Power BI - RADACAD
Power Query Performance Improvements - Test Drive - Excelerator BI
Ken Puls Explains Why Excel's Power Query Refresh Speeds Suck (powerpivotpro.com)
Regards
Phil
Proud to be a Super User!
Depends on what you are doing
Check these for reference
Speed/Performance aspects – The BIccountant
Watch Your Steps! Power Query Performance Caution for Power BI - RADACAD
Power Query Performance Improvements - Test Drive - Excelerator BI
Ken Puls Explains Why Excel's Power Query Refresh Speeds Suck (powerpivotpro.com)
Regards
Phil
Proud to be a Super User!
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 40 | |
| 35 | |
| 34 | |
| 31 | |
| 28 |
| User | Count |
|---|---|
| 137 | |
| 102 | |
| 71 | |
| 67 | |
| 65 |