Forum Discussion
Responsive ResidentIncremental refresh on computed tables in dataflows
Super UserShould I even bother with incremental refresh for the Transform layer given that the data is already loaded into the service in the extract layer?Having the data in the service and getting the data into the service are different things. If your data source is fast enough to support flush and fill then you don't need incremental refresh. If your data source is slow or very big then incremental refresh can be used if you take special care of data changes (that may not happen in the "hot" partition).
I haven't heard definitive guidance but a partition size around 200M rows seems to be a bit of a sweet spot.
RobertSlatteryHi lbendlin , thanks for the reply, but my question is specifically about guidance on incremental refresh for a dataflow that only consumes a linked entity in another dataflow in the same workspace.
In other words, the data is already loaded to the service, via incremental refresh, in the first dataflow.
The first dataflow also has enhanced compute engine forced to on to ensure query folding is an option.
- lbendlin
in that scenario there is no point in having a second dataflow, or having incremental refresh in it. (You can of course still do either if you want).
- RobertSlattery
Apologies, I should have specified that I would normally be doing more than simply aggregating, and would usually be combining dimension entities, for example, from other dataflows, with the extracted fact table. It is actually recommended by MS to have a second dataflow and I have found that I have a lot less issues if I follow that practice. The only thing missing in this article is the question I am asking here about incremental refresh.