Forum Discussion
Table Visual unable to load data despite having fewer rows.
Hi,
I have two table visuals in a report on the same page in power bi desktop. I have applied pagination to both the tables with the display of items set to 25. Each table displays 25 items on each page. In total I have data of size 3 crore rows for the first table which is working fine.
Similarly am doing the same thing for the other table which is having data of size 47lac rows. But this visual is not working, it is saying query resources limit reached. Whereas the other table is working fine despite having more data. What is the possible cause of this issue and how to go about this?
I am importing the tables from a MySQL db with maria db connector.
16 Replies
- SaiK
Helper I
- Bibiano_Geraldo
Super User
Hi SaiK ,
Probably, the second table contains some DAX calculations that are consuming a lot of resources. I recommend carefully reviewing the calculations in that table to identify any potential performance issues.
Additionally, you can use the Performance Analyzer to assess the table's performance and determine which queries or measures are impacting efficiency.
- SaiK
Helper I
Thanks for the prompt response. But this is very weird considering both the tables are using different parameters and the rest all features are same, despite having less data the table is not rendering. Shall try this out and update you about the same.
- Bibiano_Geraldo
Super User
I understand, that does seem strange, especially if the tables are using different parameters and the rest of the settings are similar. The fact that one table isn't rendering, even with less data, could be due to another factor like the complexity of the calculations or filters applied.
Try using the Performance Analyzer to identify where the issue might be, and if the calculations are correct, it might also be worth checking for any issues with the table indexes or relationships. Let me know how it goes!
- MFelix
Super User
Hi SaiK ,
This can be caused by several different things mainly the queries that you are sending to the engine that may be reaching the limit as Bibiano_Geraldo said. Without additional information is difficult to understand what is happenning.
One option can be to remove fields from the 2nd table until you get a result that way you may understand what is happening and try to focus on that specific values or set of values.
Without any specific details is difficult to pin point the root causes.