Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric certified for FREE! Don't miss your chance! Learn more

Reply
RamReddy09
New Member

I’m loading a large fact table (40–50M rows) into a Fabric Warehouse using Dataflows Gen2

I’m loading a large fact table (40–50M rows) into a Fabric Warehouse using Dataflows Gen2. The load works, but incremental refresh isn’t kicking in. Every run is doing a full reload even though I enabled incremental settings. Am I missing something?

1 ACCEPTED SOLUTION
Ugk161610
Continued Contributor
Continued Contributor

Hi @RamReddy09 ,

I ran into the same issue last month. In Dataflows Gen2, incremental refresh only works if the column you select for the ‘modified date’ is actually changing in the source.

In my case the timestamp column looked fine but wasn’t updating for late-arriving rows, so Fabric treated every row as new and reloaded everything.

 

What fixed it for me:

  • I switched the incremental column to the actual LastUpdated field from the source.

  • Cleared the staging table in the Warehouse (it still had the previous full load metadata).

  • Re-published the Dataflow and triggered a fresh run.

After that, only the changed rows got processed and the load time dropped a lot.

 

Just make sure the column you use really reflects row-level changes — Fabric relies on that to decide the delta.

 

GopiKrishna

 

View solution in original post

2 REPLIES 2
Ugk161610
Continued Contributor
Continued Contributor

Hi @RamReddy09 ,

I ran into the same issue last month. In Dataflows Gen2, incremental refresh only works if the column you select for the ‘modified date’ is actually changing in the source.

In my case the timestamp column looked fine but wasn’t updating for late-arriving rows, so Fabric treated every row as new and reloaded everything.

 

What fixed it for me:

  • I switched the incremental column to the actual LastUpdated field from the source.

  • Cleared the staging table in the Warehouse (it still had the previous full load metadata).

  • Re-published the Dataflow and triggered a fresh run.

After that, only the changed rows got processed and the load time dropped a lot.

 

Just make sure the column you use really reflects row-level changes — Fabric relies on that to decide the delta.

 

GopiKrishna

 

tayloramy
Super User
Super User

Hi @RamReddy09

 

Can you share some screenshots of your dataflow gen 2 set up? 

 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 





If you found this helpful, consider giving some Kudos.
If I answered your question or solved your problem, mark this post as the solution!

Proud to be a Super User!





Helpful resources

Announcements
Sticker Challenge 2026 Carousel

Join our Community Sticker Challenge 2026

If you love stickers, then you will definitely want to check out our Community Sticker Challenge!

Free Fabric Certifications

Free Fabric Certifications

Get Fabric certified for free! Don't miss your chance.

January Fabric Update Carousel

Fabric Monthly Update - January 2026

Check out the January 2026 Fabric update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.