March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Consider this scenario: a data source with incremental refresh policy enabled, no last-update-time field, the refresh time range is 3 days, and archive is 6 months. After prolonged normal operations (i.e. all data is in place), the refresh starts to consistently fail and after a few failed attempts it gets auto-disabled by the system. If the model remains in this disabled state for, let's say 14 days, what will happen after things get back to normal: will there be a gap in the data between day 3 and day 14, or will the service detect the gap and fill it in?
I couldn't find any documentation detailing this scenario, but just a read of the documentation seems to suggest that there will be a gap.
A pointer to some literature describing this or an account of personal experience of this situation is appreciated.
Solved! Go to Solution.
Hi, @beranes
If the incremental refresh policy is in place, and the refresh operation consistently fails to cause auto-disable, any data that was not refreshed during the outage will not be automatically backfilled after the refresh is resumed. This means that, depending on your scenario, if refresh has been disabled for 14 days, there will indeed be a gap in the data between days 3 and 14.
An incremental refresh policy is designed to refresh data within a specified refresh range, in this case 3 days. Once the system is back to normal and refreshes resume, it will continue to apply the policy based on the current date and will not retroactively populate data for time periods where refreshes did not occur.
To address this gap, you'll need to manually trigger a refresh for the affected time period. You can do this by adjusting the and parameters to cover the interval in Power BI Desktop, and then republishing the report to the Power BI service. After a manual refresh, you can reset the parameters to the original settings. For more information on configuring incremental refresh and handling data gaps, you can check out the link:
How to Get Your Question Answered Quickly
Best Regards
Yongkang Hua
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi, @beranes
If the incremental refresh policy is in place, and the refresh operation consistently fails to cause auto-disable, any data that was not refreshed during the outage will not be automatically backfilled after the refresh is resumed. This means that, depending on your scenario, if refresh has been disabled for 14 days, there will indeed be a gap in the data between days 3 and 14.
An incremental refresh policy is designed to refresh data within a specified refresh range, in this case 3 days. Once the system is back to normal and refreshes resume, it will continue to apply the policy based on the current date and will not retroactively populate data for time periods where refreshes did not occur.
To address this gap, you'll need to manually trigger a refresh for the affected time period. You can do this by adjusting the and parameters to cover the interval in Power BI Desktop, and then republishing the report to the Power BI service. After a manual refresh, you can reset the parameters to the original settings. For more information on configuring incremental refresh and handling data gaps, you can check out the link:
How to Get Your Question Answered Quickly
Best Regards
Yongkang Hua
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
133 | |
90 | |
88 | |
64 | |
58 |
User | Count |
---|---|
201 | |
137 | |
107 | |
70 | |
68 |