Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Simply - What parts of a PBIX report dictate its size when it comes to re-freshing.
I'm hitting an issue with our overnight server refresh, as the report I have created is hitting the memory limit for our business. There is an option to pay to upgrade, but at the moment thats not an option being persued so optimising this report is required.
Curious what factors are most common in causing this memory size issue. Is it the number of data connections, the size of those connections, the number of table &/or mesure calculations...
Interested where is best to start looking/testing.
Note - I can refresh this report on my desktop without issue 🙂
Solved! Go to Solution.
The memory allocation required during a refresh is dependant on the tables, columns and relationships in your model. Measures do not impact on the memory needed during refresh as they are only evaluated during queries. If you want to get an idea of what parts of your model(s) are using the most memory you could use a tool like Vertipaq Analyzer https://www.sqlbi.com/tools/vertipaq-analyzer/
The memory allocation required during a refresh is dependant on the tables, columns and relationships in your model. Measures do not impact on the memory needed during refresh as they are only evaluated during queries. If you want to get an idea of what parts of your model(s) are using the most memory you could use a tool like Vertipaq Analyzer https://www.sqlbi.com/tools/vertipaq-analyzer/
User | Count |
---|---|
141 | |
113 | |
104 | |
78 | |
64 |
User | Count |
---|---|
136 | |
125 | |
107 | |
70 | |
61 |