Incremental refresh in licence pro

[VitalyBalabanov]

Hii, i have a few issues about Incremental refresh in licence pro :

1.I need charge to service couple heavy tables with incremntal refresh, if I need to create couple variables like RangeStart1, RangeEnd1, RangeStart2, RangeEnd2 or use only ones  RangeStart, RangeEnd on couple tables?

2.After changing something in power Desktop and charge it to service, incremntal refresh charge like first time and it take long time, can I do something with this? 

[v-diye-msft · Accepted solution]

Hi @VitalyBalabanov 

1. You can create ones  RangeStart, RangeEnd and implement to several tables. 

2. The first refresh in the Power BI service may take longer to import all five full calendar years. Subsequent refreshes may be finished in a fraction of the time.

If you'd like to speed up the pregress, you might enabled the query folding function. note that:

It's important the partition filters are pushed to the source system when queries are submitted for refresh operations. To push filtering down means the datasource should support query folding. Most data sources that support SQL queries support query folding. However, data sources like flat files, blobs, and web feeds typically do not. In cases where the filter is not supported by the datasource back-end, it cannot be pushed down. In such cases, the mashup engine compensates and applies the filter locally, which may require retrieving the full dataset from the data source. This can cause incremental refresh to be very slow, and the process can run out of resources either in the Power BI service or in the on-premises data gateway if used.

If you want to check that the necessary query folding is occurring, you can use the Query Diagnostics feature, or trace queries received by the source database.

Refer to the detailed official document for more reference:

https://docs.microsoft.com/en-us/power-bi/admin/service-premium-incremental-refresh