topic QlikView Internal Architecture in QlikView https://community.qlik.com/t5/QlikView/QlikView-Internal-Architecture/m-p/175277#M43781 <HTML><HEAD></HEAD><BODY><P>Anyone can help me on this????</P><P></P><P></P></BODY></HTML> Thu, 26 Aug 2010 09:40:22 GMT 2010-08-26T09:40:22Z QlikView Internal Architecture https://community.qlik.com/t5/QlikView/QlikView-Internal-Architecture/m-p/175276#M43780 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P>Any idea how QlikView stores the data in Memmory and process the data. I am looking for the internal Architecture of QlikView.</P><P></P><P>Regards,</P><P>XXX</P></BODY></HTML> Thu, 26 Aug 2010 07:32:46 GMT https://community.qlik.com/t5/QlikView/QlikView-Internal-Architecture/m-p/175276#M43780 2010-08-26T07:32:46Z QlikView Internal Architecture https://community.qlik.com/t5/QlikView/QlikView-Internal-Architecture/m-p/175277#M43781 <HTML><HEAD></HEAD><BODY><P>Anyone can help me on this????</P><P></P><P></P></BODY></HTML> Thu, 26 Aug 2010 09:40:22 GMT https://community.qlik.com/t5/QlikView/QlikView-Internal-Architecture/m-p/175277#M43781 2010-08-26T09:40:22Z QlikView Internal Architecture https://community.qlik.com/t5/QlikView/QlikView-Internal-Architecture/m-p/175278#M43782 <HTML><HEAD></HEAD><BODY><P>Can any one help me on this??</P></BODY></HTML> Thu, 26 Aug 2010 10:53:09 GMT https://community.qlik.com/t5/QlikView/QlikView-Internal-Architecture/m-p/175278#M43782 2010-08-26T10:53:09Z Re: QlikView Internal Architecture https://community.qlik.com/t5/QlikView/QlikView-Internal-Architecture/m-p/175279#M43783 <HTML><HEAD></HEAD><BODY><P><EM style="font-family: trebuchet ms,geneva;">Hi,</EM></P><P></P><P><EM style="font-family: trebuchet ms,geneva;">I understand this is very old post. However, I thought I would share my understanding if you are still interested to know. </EM></P><P></P><P><EM style="font-family: trebuchet ms,geneva;">The data records are read into the memory, so that all the processing of data may be done through memory. I am sure you know this bit. QlikView treats all the data as Data Element Type (Columns / Fields) and Data Element Values (Values / Records). So each different data element value of each data element type is assigned a binary code and the data records are stored in binary-coded form and they are also sorted. By using the binary coding, very quick searches can be done on the tables. Also, QlikView removes the redundant information information and reduces the amount of data. However, the redundant information in stored as seperately with the frequencies for each unique data element value and across each data element type. When user makes a selection on data element values then the implied selection (possible values) are kept track seperately to present them to the user. By this process QlikView can perform rapid linear searches. </EM></P><P></P><P><EM style="font-family: trebuchet ms,geneva;">I understand this is not in detail but just a quick overview. I hope this helps!</EM></P><P></P><P><EM style="font-family: trebuchet ms,geneva;">Good luck!</EM></P><P></P><P><EM style="font-family: trebuchet ms,geneva;">Cheers - DV</EM></P></BODY></HTML> Thu, 13 Oct 2011 08:47:24 GMT https://community.qlik.com/t5/QlikView/QlikView-Internal-Architecture/m-p/175279#M43783 IAMDV 2011-10-13T08:47:24Z