Forum Discussion
Ranking
Yes. You need to aggregate the data so that the rows returned are below that limit.
This may be a stupid question, but no question is stupid right...:smileyhappy:
How do I aggregate the data?
would i break the table into x number of tables, where x is the number of companies in the database? so each company has its own table and therefore its own information, then link them back up inside Power BI?
- dkay84_PowerBI9 years agoMicrosoft Employee
Direct Query is designed more to return aggregations that the source DB performs, rather than return the raw data. While filtering always consumes a lot of resources, with an import data model (rather than DQ) it is possible that your structure/model is partly to blame for the performance problems. You should be using a star schema with lookup tables and fact tables. I would recommend going back to an import data model and seeing if you can improve the model structure to get a better response time when slicing the data.