Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
jimbo20814
Creator
Creator

Processing slowness and best practices

All, all the lookups load very quickly, but the main process flow is very very slow, moving just a few records at a time. In the example below, UserDomain has 70,0001 records but it's taken several minutes just to get to 2215. Why does it process so slow and is there another design (best practice) which can make faster?

 

0683p000009Ma2U.png

Labels (2)
1 Reply
TRF
Champion II
Champion II

Lookup are just reading while main process is writing in some tables, this should be a reason.
If you use jdts driver, switch to official MS SQL driver which is faster.
At design level, maybe you should store output in memory to limite tDBOutput operations.