topic Mapping LOAD with two fields, no processing - not optimized? in QlikView https://community.qlik.com/t5/QlikView/Mapping-LOAD-with-two-fields-no-processing-not-optimized/m-p/67420#M11126 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P></P><P>I have been working on an app where several mapping LOADs used to take quite long. I changed the order of execution a bit and used a temporary table which is now loaded optimized, resulting in a mayor speedup for the whole thing.</P><P>The one that is taking the longest now is a mapping LOAD again with just two fields and no processing, coming from an "original" qvd (straight from SAP) via a relative path as is usual in our system. I wonder, why is this not optimized?</P><P>I will try, maybe with a PRECEDING LOAD or something.</P><P>Does anyone have any idea why this is so?</P><P>Thanks a lot!</P><P>Best regards,</P><P></P><P>DataNibbler</P></BODY></HTML> Tue, 08 May 2018 07:55:52 GMT datanibbler 2018-05-08T07:55:52Z Mapping LOAD with two fields, no processing - not optimized? https://community.qlik.com/t5/QlikView/Mapping-LOAD-with-two-fields-no-processing-not-optimized/m-p/67420#M11126 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P></P><P>I have been working on an app where several mapping LOADs used to take quite long. I changed the order of execution a bit and used a temporary table which is now loaded optimized, resulting in a mayor speedup for the whole thing.</P><P>The one that is taking the longest now is a mapping LOAD again with just two fields and no processing, coming from an "original" qvd (straight from SAP) via a relative path as is usual in our system. I wonder, why is this not optimized?</P><P>I will try, maybe with a PRECEDING LOAD or something.</P><P>Does anyone have any idea why this is so?</P><P>Thanks a lot!</P><P>Best regards,</P><P></P><P>DataNibbler</P></BODY></HTML> Tue, 08 May 2018 07:55:52 GMT https://community.qlik.com/t5/QlikView/Mapping-LOAD-with-two-fields-no-processing-not-optimized/m-p/67420#M11126 datanibbler 2018-05-08T07:55:52Z Re: Mapping LOAD with two fields, no processing - not optimized? https://community.qlik.com/t5/QlikView/Mapping-LOAD-with-two-fields-no-processing-not-optimized/m-p/67421#M11127 <HTML><HEAD></HEAD><BODY><P>Curious - with a small temp_table, loading the mapping_table resident from this, the temp_table is suddenly optimized, running much faster, and the mapping_table is faster, too (the mapping in total now takes 6sec, it used to be 32).</P><P>What is the reason for this? Is this generally so? Can I write that in my "best practices" catalog as something that should be done?</P></BODY></HTML> Tue, 08 May 2018 08:02:16 GMT https://community.qlik.com/t5/QlikView/Mapping-LOAD-with-two-fields-no-processing-not-optimized/m-p/67421#M11127 datanibbler 2018-05-08T08:02:16Z