This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 6%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESU%3C/text%3E%3C/svg%3E)
I want to limit the data refresh while refreshing in On premises PowerBI
I have this visual for each dashboard that on which data time it was last refreshed, so now when I want to refresh again, I want to refresh the data only after the mentioned date time to avoid too much time taking while refreshing, for now whenever I refresh the dashboard it takes the same time whether last refresh was an hour ago or a year ago
Please guide how can I achieve this.
A Microsoft online analytical data engine used in decision support and business analytics, providing the analytical data for business reports and client applications such as Power BI, Excel, Reporting Services reports, and other data visualization tools.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 63%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDD%3C/text%3E%3C/svg%3E)
Use incremental refresh:
Create two Date/Time parameters named exactly RangeStart and RangeEnd.
Filter your fact table's datetime column: ≥ RangeStart and < RangeEnd.
Right-click table then Incremental refresh then set archive window (e.g.5 years) and refresh window (e.g.3 days).
From where are retrieving the data? An SQL Server database? I will assume the latter (since that is the environment I'm familiar with).
It is not as simple as it may sound. First of all, there must be a way to safely discern changes in the tables you are reading from. That is, there must be a rowversion column or something like a LastUpdated. rowversion is not that very common, but since such columns are maintained by the engine, they are more reliable. A LastUpdated column requires that all code that touches the row explicitly updates the column, and this includes manual updates.
There are also special feature to help you retrieve changes such Change Data Capture and Change Tracking. They can be very helpful, but they also take time to set up and learn.
Another challenge is that updates may occur when you are reading, and depending on how you retrieve your high-water marks, you may fail to get some of those updates.
Yet an issue is that if you make a partial refresh of the data, you may need to recalculate aggregations etc.
So it is not exactly a small project.