<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Pack Distinct String Values for better performance - Any Ideas? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Pack-Distinct-String-Values-for-better-performance-Any-Ideas/m-p/214516#M68063</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;we are planning to use QlikView to analyze our product data. I did already some tests and I've figured out, that we have got one main problem.&lt;/P&gt;&lt;P&gt;Our serial number before 2010 starts with a 0. Examples are 091212121234 or 08010101122342 or A24323454. We have got already approx. 25 mio SNs in a lot of different databases. While doing the tests, I have recognized, that those distinct String Values consume a lot of memory and performance.&lt;/P&gt;&lt;P&gt;Does anybody has got experience how to store this as number and show it, like reading it? Is there a way with dual or / and autonumber?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Apr 2010 20:16:38 GMT</pubDate>
    <dc:creator />
    <dc:date>2010-04-14T20:16:38Z</dc:date>
    <item>
      <title>Pack Distinct String Values for better performance - Any Ideas?</title>
      <link>https://community.qlik.com/t5/QlikView/Pack-Distinct-String-Values-for-better-performance-Any-Ideas/m-p/214516#M68063</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;we are planning to use QlikView to analyze our product data. I did already some tests and I've figured out, that we have got one main problem.&lt;/P&gt;&lt;P&gt;Our serial number before 2010 starts with a 0. Examples are 091212121234 or 08010101122342 or A24323454. We have got already approx. 25 mio SNs in a lot of different databases. While doing the tests, I have recognized, that those distinct String Values consume a lot of memory and performance.&lt;/P&gt;&lt;P&gt;Does anybody has got experience how to store this as number and show it, like reading it? Is there a way with dual or / and autonumber?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Apr 2010 20:16:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Pack-Distinct-String-Values-for-better-performance-Any-Ideas/m-p/214516#M68063</guid>
      <dc:creator />
      <dc:date>2010-04-14T20:16:38Z</dc:date>
    </item>
    <item>
      <title>Pack Distinct String Values for better performance - Any Ideas?</title>
      <link>https://community.qlik.com/t5/QlikView/Pack-Distinct-String-Values-for-better-performance-Any-Ideas/m-p/214517#M68064</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Christian,&lt;/P&gt;&lt;P&gt;You can use autonumberhash128 (or 256) to reduce the memory used by SN. But in this case you cannot show them as is anymore - they will be replaced with numbers. I think that making it "dual" will not help because you're adding short data to long, not repalcing it.&lt;/P&gt;&lt;P&gt;Frankly, this sort of data should not be a problem unless you have tens of millions of them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Apr 2010 01:41:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Pack-Distinct-String-Values-for-better-performance-Any-Ideas/m-p/214517#M68064</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-04-15T01:41:39Z</dc:date>
    </item>
    <item>
      <title>Pack Distinct String Values for better performance - Any Ideas?</title>
      <link>https://community.qlik.com/t5/QlikView/Pack-Distinct-String-Values-for-better-performance-Any-Ideas/m-p/214518#M68065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;autonumberhash is a good idea for the key. Thanks! This is really looking good.&lt;/P&gt;&lt;P&gt;There are tens of million of distinct values, so it is a problem. Certainly not for a well suited server, but my 32bit notebook with 4gb of memory comes to its limits, when loading 8 million rows with some more attributes. As this is quite unuasual (I've loaded already 20 million rows with a much older notebook with 1.5gb), I am continuing to find ways to optimize memory consumption.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Apr 2010 21:33:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Pack-Distinct-String-Values-for-better-performance-Any-Ideas/m-p/214518#M68065</guid>
      <dc:creator />
      <dc:date>2010-04-15T21:33:57Z</dc:date>
    </item>
  </channel>
</rss>

