Forum Discussion
Long Refresh
Hi,
I have a kinda big power bi desktop model (880mb).
When i schedule a refresh on the service sometimes it work and sometimes it fails on timeout.
My question is how can i tell what table takes the longest to refresh? and are there any any "first aid" solutions so my refresh will not fail?
Hi Anonymous ,
You can try the Performance Analyzer or DAX Studio to see the execution time of queries and find the queries that take the longest time to optimize.
Analyzing a slow report query in DAX Studio
In addition, you can try this way to calculate the refresh time for each table.
How to track refresh time in Power BI Desktop
If the problem is still not resolved, please provide detailed error information or the expected result you expect. Let me know immediately, looking forward to your reply.
Best Regards,
Winniz
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
3 Replies
- VahidDMSuper User
Hi Anonymous
You can use implement incremental refresh with the dataset.
https://docs.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-overviewIncremental refresh extends scheduled refresh operations by providing automated partition creation and management for dataset tables that frequently load new and updated data. For most datasets, this is one or more tables that contain transaction data that changes often and can grow exponentially, like a fact table in a relational or star database schema. An incremental refresh policy to partition the table, refreshing only the most recent import partition(s), and optionally leveraging an additional DirectQuery partition for real-time data can significantly reduce the amount of data that has to be refreshed while at the same time ensuring that even the latest changes at the data source are included in the query results.
With incremental refresh and real-time data:
- Fewer refresh cycles for fast-changing data ā DirectQuery mode gets the latest data updates as queries are processed without requiring a high refresh cadence.
- Refreshes are faster - Only the most recent data that has changed needs to be refreshed.
- Refreshes are more reliable - Long-running connections to volatile data sources aren't necessary. Queries to source data run faster, reducing potential for network problems to interfere.
- Resource consumption is reduced - Less data to refresh reduces overall consumption of memory and other resources in both Power BI and data source systems.
- Enables large datasets - Datasets with potentially billions of rows can grow without the need to fully refresh the entire dataset with each refresh operation.
- Easy setup - Incremental refresh policies are defined in Power BI Desktop with just a few tasks. When published, the service automatically applies those policies with each refresh.
If this post helps, please consider accepting it as the solution to help the other members find it more quickly.
Appreciate your Kudos!!
LinkedIn: www.linkedin.com/in/vahid-dm/ - AnonymousNot applicable
Thanks, i will look it up and hope it works.
But i would still like to know if there is a way to know what takes longer to refresh? so i wil know where to focus first.
- v-kkf-msftCommunity Support
Hi Anonymous ,
You can try the Performance Analyzer or DAX Studio to see the execution time of queries and find the queries that take the longest time to optimize.
Analyzing a slow report query in DAX Studio
In addition, you can try this way to calculate the refresh time for each table.
How to track refresh time in Power BI Desktop
If the problem is still not resolved, please provide detailed error information or the expected result you expect. Let me know immediately, looking forward to your reply.
Best Regards,
Winniz
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.