<?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 Re: Composite key in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377391#M821877</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;I have an old application in legacy. And there are lot of this kind keys (&amp;amp;' '&amp;amp;). This Application has three or four hours update time.&lt;/P&gt;&lt;P&gt;I think if I change them, I lower the update time and physical size of application.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 10 Aug 2017 07:34:41 GMT</pubDate>
    <dc:creator>antonaks</dc:creator>
    <dc:date>2017-08-10T07:34:41Z</dc:date>
    <item>
      <title>Composite key</title>
      <link>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377388#M821874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN lang="en"&gt;Dear colleagues. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="en"&gt;I want to ask you how best to create a composite key, to save resources.&lt;BR /&gt;&lt;SPAN&gt;&lt;STRONG&gt;AutoNumberHash128 ()&lt;/STRONG&gt; or by connecting strings&lt;STRONG&gt; [fileld_1] &amp;amp; ' ' &amp;amp; [fileld_2]&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2020 16:16:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377388#M821874</guid>
      <dc:creator>antonaks</dc:creator>
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Composite key</title>
      <link>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377389#M821875</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Certain better option is: &lt;STRONG style="font-size: 13px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;AutoNumberHash128 ()&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Aug 2017 07:20:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377389#M821875</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2017-08-10T07:20:34Z</dc:date>
    </item>
    <item>
      <title>Re: Composite key</title>
      <link>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377390#M821876</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Anton,&lt;/P&gt;&lt;P&gt;I would go for autonumber e.g.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Autonumber([fileld_1] &amp;amp; '|' &amp;amp; [fileld_2],'AutoID1_2') as AutoID1_2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using the '|' as a separator is a good practice unless that symbol is used in any of the fields you are making the composite key out of. The parameter 'AutoID1_2' is just to keep separate this autonumber sequence from any others you might be creating in your script&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andrew&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Aug 2017 07:23:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377390#M821876</guid>
      <dc:creator>effinty2112</dc:creator>
      <dc:date>2017-08-10T07:23:39Z</dc:date>
    </item>
    <item>
      <title>Re: Composite key</title>
      <link>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377391#M821877</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;I have an old application in legacy. And there are lot of this kind keys (&amp;amp;' '&amp;amp;). This Application has three or four hours update time.&lt;/P&gt;&lt;P&gt;I think if I change them, I lower the update time and physical size of application.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Aug 2017 07:34:41 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377391#M821877</guid>
      <dc:creator>antonaks</dc:creator>
      <dc:date>2017-08-10T07:34:41Z</dc:date>
    </item>
    <item>
      <title>Re: Composite key</title>
      <link>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377392#M821878</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, with other possible improvement areas, if you try &lt;STRONG&gt;autonumber&lt;/STRONG&gt;ing, you should see an improvement in file size. However, I would also suggest to be careful of other nuisances of the same like 'load order dependency' (if using without &lt;STRONG&gt;hash&lt;/STRONG&gt;.. read here: &lt;A href="https://community.qlik.com/thread/146395"&gt;AutoNumber() vs Auto..Hash()&lt;/A&gt; )&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Aug 2017 07:44:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377392#M821878</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2017-08-10T07:44:13Z</dc:date>
    </item>
    <item>
      <title>Re: Composite key</title>
      <link>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377393#M821879</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;AutoNumber is always better because when we create an composite Key as &lt;STRONG style="font-size: 13px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;[fileld_1] &amp;amp; ' ' &amp;amp; [fileld_2] , &lt;/STRONG&gt;then for each and every unique Key it will assign a memory and pointer an will consider as an String.&lt;/P&gt;&lt;P&gt;and when we use Autonumber it will consider is as number.&lt;/P&gt;&lt;P&gt;And Number consume less space then string.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vanraj Dinesh Bohra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Aug 2017 09:21:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377393#M821879</guid>
      <dc:creator>bohravanraj</dc:creator>
      <dc:date>2017-08-10T09:21:14Z</dc:date>
    </item>
    <item>
      <title>Re: Composite key</title>
      <link>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377394#M821880</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN lang="en"&gt;Thank you colleagues. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="en"&gt;&lt;SPAN&gt;I realized that the potential for optimization I have with my legacy is great.&lt;/SPAN&gt; Starting with the keys and ending with redundant data. &lt;SPAN class="alt-edited"&gt;I will continue to work.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Aug 2017 09:35:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377394#M821880</guid>
      <dc:creator>antonaks</dc:creator>
      <dc:date>2017-08-10T09:35:34Z</dc:date>
    </item>
    <item>
      <title>Re: Composite key</title>
      <link>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377395#M821881</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;&lt;SPAN&gt;Thanks for the link.&lt;/SPAN&gt; &lt;SPAN&gt;Very interesting.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Aug 2017 09:36:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Composite-key/m-p/1377395#M821881</guid>
      <dc:creator>antonaks</dc:creator>
      <dc:date>2017-08-10T09:36:58Z</dc:date>
    </item>
  </channel>
</rss>

