topic Re: Explain the optimize and non-optimze load in qvd with examples ? in QlikView https://community.qlik.com/t5/QlikView/Explain-the-optimize-and-non-optimze-load-in-qvd-with-examples/m-p/806709#M284790 <HTML><HEAD></HEAD><BODY><P style="margin-bottom: .0001pt;"><SPAN style="font-size: 11pt; font-family: Calibri, sans-serif;">Hi Harish,</SPAN></P><P></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">Optimized load is much faster and therefore preferable, especially for larger data sets. Optimized loads are possible if no transformations (calculations) are made during the load, and no (almost) filtering is done in a WHERE clause. The only acceptable filter is using function Exists: WHERE Exists(Field)</SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;"> So for example this load can't be optimized: Load * From ... WHERE Country = 'US' </SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">but this load can be optimized: Load * From ... WHERE EXISTS(Country)</SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">On the other hand, the only time you want the load not to be optimized, is if you load a Mapping table from a QVD file. In this case, Optimized load doesn't quite work, so you want to make the load non-optimized deliberately.</SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;"><BR /></SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">Some examples of things that will cause a non-optimised load are:</SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;"><BR /></SPAN></P><P><SPAN style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;"> - Adding new fields to the table<BR /> - Deriving new values from a field in the QVD<BR /> - Retrieving a field twice<BR /> - Most WHERE conditions<BR /> - Joining to an existing in memory table<BR /> - Loading data into a mapping table</SPAN></P><P><SPAN style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;"><BR /></SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">In contrast the things you are allowed to do are:</SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">- Rename fields<BR /> - Omit fields<BR /> - Do a simple one field WHERE EXISTS on a field returned in the record set</SPAN></P><P></P><P style="margin-bottom: .0001pt;">Regards</P><P style="margin-bottom: .0001pt;">Neetha</P></BODY></HTML> Wed, 10 Dec 2014 14:16:48 GMT Anonymous 2014-12-10T14:16:48Z Explain the optimize and non-optimze load in qvd with examples ? https://community.qlik.com/t5/QlikView/Explain-the-optimize-and-non-optimze-load-in-qvd-with-examples/m-p/806707#M284788 <HTML><HEAD></HEAD><BODY><P>Explain the optimize and non-optimze load in qvd with examples ?</P></BODY></HTML> Wed, 10 Dec 2014 14:10:14 GMT https://community.qlik.com/t5/QlikView/Explain-the-optimize-and-non-optimze-load-in-qvd-with-examples/m-p/806707#M284788 2014-12-10T14:10:14Z Re: Explain the optimize and non-optimze load in qvd with examples ? https://community.qlik.com/t5/QlikView/Explain-the-optimize-and-non-optimze-load-in-qvd-with-examples/m-p/806708#M284789 <HTML><HEAD></HEAD><BODY><P>Perhaps you should Google the answers to your homework. The search facility here is quite useful too. <IMG src="https://community.qlik.com/legacyfs/online/emoticons/wink.png" /></P></BODY></HTML> Wed, 10 Dec 2014 14:15:16 GMT https://community.qlik.com/t5/QlikView/Explain-the-optimize-and-non-optimze-load-in-qvd-with-examples/m-p/806708#M284789 ThornOfCrowns 2014-12-10T14:15:16Z Re: Explain the optimize and non-optimze load in qvd with examples ? https://community.qlik.com/t5/QlikView/Explain-the-optimize-and-non-optimze-load-in-qvd-with-examples/m-p/806709#M284790 <HTML><HEAD></HEAD><BODY><P style="margin-bottom: .0001pt;"><SPAN style="font-size: 11pt; font-family: Calibri, sans-serif;">Hi Harish,</SPAN></P><P></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">Optimized load is much faster and therefore preferable, especially for larger data sets. Optimized loads are possible if no transformations (calculations) are made during the load, and no (almost) filtering is done in a WHERE clause. The only acceptable filter is using function Exists: WHERE Exists(Field)</SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;"> So for example this load can't be optimized: Load * From ... WHERE Country = 'US' </SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">but this load can be optimized: Load * From ... WHERE EXISTS(Country)</SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">On the other hand, the only time you want the load not to be optimized, is if you load a Mapping table from a QVD file. In this case, Optimized load doesn't quite work, so you want to make the load non-optimized deliberately.</SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;"><BR /></SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">Some examples of things that will cause a non-optimised load are:</SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;"><BR /></SPAN></P><P><SPAN style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;"> - Adding new fields to the table<BR /> - Deriving new values from a field in the QVD<BR /> - Retrieving a field twice<BR /> - Most WHERE conditions<BR /> - Joining to an existing in memory table<BR /> - Loading data into a mapping table</SPAN></P><P><SPAN style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;"><BR /></SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">In contrast the things you are allowed to do are:</SPAN></P><P><SPAN lang="EN-US" style="font-size: 11.0pt; font-family: 'Calibri','sans-serif'; color: black;">- Rename fields<BR /> - Omit fields<BR /> - Do a simple one field WHERE EXISTS on a field returned in the record set</SPAN></P><P></P><P style="margin-bottom: .0001pt;">Regards</P><P style="margin-bottom: .0001pt;">Neetha</P></BODY></HTML> Wed, 10 Dec 2014 14:16:48 GMT https://community.qlik.com/t5/QlikView/Explain-the-optimize-and-non-optimze-load-in-qvd-with-examples/m-p/806709#M284790 Anonymous 2014-12-10T14:16:48Z Re: Explain the optimize and non-optimze load in qvd with examples ? https://community.qlik.com/t5/QlikView/Explain-the-optimize-and-non-optimze-load-in-qvd-with-examples/m-p/806710#M284791 <HTML><HEAD></HEAD><BODY><P>Hi</P><P></P><P>Here is a blog post which will be helpful</P><P></P><P><A href="http://www.quickintelligence.co.uk/qlikview-optimised-qvd-loads/" title="http://www.quickintelligence.co.uk/qlikview-optimised-qvd-loads/">http://www.quickintelligence.co.uk/qlikview-optimised-qvd-loads/</A></P><P></P><P></P><P>Best Regards,</P><P>Gabriel</P></BODY></HTML> Wed, 10 Dec 2014 14:17:52 GMT https://community.qlik.com/t5/QlikView/Explain-the-optimize-and-non-optimze-load-in-qvd-with-examples/m-p/806710#M284791 Gabriel 2014-12-10T14:17:52Z