Forum Discussion
Incremental Refresh Woes
Hello v-yingjl . It turns out that the nature of this data is such that at least 1 row from virtually all historical partitions gets updated each day (thereby causing all partions--the whole data table--to be refreshed each day). In addition, the field I was using for Detect Data Changes was not indexed. Those 2 factors amounted to combo knockout punch, so to speak. So I've stopped using Detect Data Changes for now until the DBAs can add the correct update field and index it. That will at least address 1 of the 2 factors; can't do much about so much of the past getting updated everyday. If that's not enough then I will just abandon the Detect Data Changes option and possibly even IR altogether.
Hi robarivas ,
- When you configure incremental refresh and publish the report to power bi service, you can now refresh the model. The first refresh may take longer to import the historical data. Subsequent refreshes can be much quicker because they use incremental refresh. Please refer this article: Ensuring-your-power-bi-incremental-refresh-does-not-timeout
- The troubleshooting refresh article explains that refresh operations in the Power BI service are subject to timeouts. Queries can also be limited by the default timeout for the data source. Please refer this microsoft document: Incremental refresh timeout
- If the refresh timeouts, please consider breaking the dataset into smaller pieces.
Best Regards,
Yingjie Li
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.