Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
jagadeesh_diamo
Contributor III
Contributor III

Significance of Incremental load vs Full load

Hello expect,

I have QVD maker which extract almost 10 Fact tables. Just taking one Fact as an example to explain the issue.

Full:

No of Records: 5 million (taking 2 min) - Database connect time 2min

Incremental load:

No of records: 10000 (taking 20sec) - Database connect time 20sec

However to concatenate regular QVD to incremental block and to finish total process - overall time is taking 5min.

All Fact table full load - 25min

Incremental load - 1 hr 40min.

My observation here is, when we do full load we can finish load with less time however we connect to DB all the time. When we go for incremental load, we connect to DB less time but overall load to make QVD is more.

So, which approach is better, please reply expert.

3 Replies
jagadeesh_diamo
Contributor III
Contributor III
Author

Sorry for typo...

Please read...

Hello Experts...

marcus_sommer

There will be something quite wrong within your approach and a correct implemented incremental load-approach will reduce the load-time significantly and not the opposite. Take a look here: Advanced topics for creating a qlik datamodel on the last two links-blocks which gives various examples on incremenatl loadings and optimized loadings of qvd's.

- Marcus

jagadeesh_diamo
Contributor III
Contributor III
Author

Might be true Marcus. Let me review it.

While concatenating full QVD with inserted Block QVD, it is taking more time. I will cross check whole approach once. Thanks a lot.