topic Is it a Real Data Compression? or Just a Pointer Memory Model? in QlikView https://community.qlik.com/t5/QlikView/Is-it-a-Real-Data-Compression-or-Just-a-Pointer-Memory-Model/m-p/705835#M1074664 <HTML><HEAD></HEAD><BODY><P>It was really interesting to know QlikView's Data Compression logic, in the form of Data table, Symbol table, Bit-stuffed pointers, and Vectors to track current selections, relevant and not-relevant.</P><P></P><P>As mentioned by HIC, it's really sensible that this data compression logic goes well with redundant data than discrete one. I don't see any data compression (apart from the bit-stuffed pointers, it may be compressed), i was thinking that there was an algorithm followed to do data compression. But still, this bit-stuffed pointer approach is really amazing, and really surprised how come the traditional BI giants not thinking about this approach? </P><P></P><P>It would be great insight to know in bit detail about: In-memory or Associative (QlikView), Out-Memory or Joins (Direct Discovery) and the Hybrid (Both in-memory and out-memory) data model. <STRONG><EM>Especially, how the hybrid approach, both Associative and Joins handled together?</EM></STRONG> would be a great help. Please, direct me.</P><P></P><P>Regards,</P><P>-Vijay</P></BODY></HTML> Mon, 04 Aug 2014 06:57:31 GMT 2014-08-04T06:57:31Z Is it a Real Data Compression? or Just a Pointer Memory Model? https://community.qlik.com/t5/QlikView/Is-it-a-Real-Data-Compression-or-Just-a-Pointer-Memory-Model/m-p/705835#M1074664 <HTML><HEAD></HEAD><BODY><P>It was really interesting to know QlikView's Data Compression logic, in the form of Data table, Symbol table, Bit-stuffed pointers, and Vectors to track current selections, relevant and not-relevant.</P><P></P><P>As mentioned by HIC, it's really sensible that this data compression logic goes well with redundant data than discrete one. I don't see any data compression (apart from the bit-stuffed pointers, it may be compressed), i was thinking that there was an algorithm followed to do data compression. But still, this bit-stuffed pointer approach is really amazing, and really surprised how come the traditional BI giants not thinking about this approach? </P><P></P><P>It would be great insight to know in bit detail about: In-memory or Associative (QlikView), Out-Memory or Joins (Direct Discovery) and the Hybrid (Both in-memory and out-memory) data model. <STRONG><EM>Especially, how the hybrid approach, both Associative and Joins handled together?</EM></STRONG> would be a great help. Please, direct me.</P><P></P><P>Regards,</P><P>-Vijay</P></BODY></HTML> Mon, 04 Aug 2014 06:57:31 GMT https://community.qlik.com/t5/QlikView/Is-it-a-Real-Data-Compression-or-Just-a-Pointer-Memory-Model/m-p/705835#M1074664 2014-08-04T06:57:31Z