<?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 Incremental load performance low on big table in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Incremental-load-performance-low-on-big-table/m-p/391157#M698937</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a Qlikview application with incremental load (using primary key and field datetime on tables).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a data volume which become important : neat 350 000 000 lines on some table using incremental load.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My application must keep one year history, and load daily near 4 million of lines using incremental load.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I see that the incremental load seems as long as the full load which is not really interesting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could it be possible to optimize this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have though about to use a BIT field instead of datetime field for the incremental load. And set an index on the field on database table I load.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The process will be something like this, for a BIT field ToLoad on a table with incremental load used:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1-all updated/inserted lines in table -&amp;gt; the field ToLoad set to 1 on the lines&lt;/P&gt;&lt;P&gt;2-QlikView application refresh with incremental condition on field "ToLoad=True"&lt;/P&gt;&lt;P&gt;3-Field ToLoad set to 0 on all the table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you think it will works better? Or any better idea?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The datetime method has truly poor performance on huge data volume as even if you set an index on a datetime field it's not really increase performance (all the value are different, the index has as values as number of table lines).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you help me?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 Nov 2012 13:04:02 GMT</pubDate>
    <dc:creator />
    <dc:date>2012-11-29T13:04:02Z</dc:date>
    <item>
      <title>Incremental load performance low on big table</title>
      <link>https://community.qlik.com/t5/QlikView/Incremental-load-performance-low-on-big-table/m-p/391157#M698937</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a Qlikview application with incremental load (using primary key and field datetime on tables).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a data volume which become important : neat 350 000 000 lines on some table using incremental load.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My application must keep one year history, and load daily near 4 million of lines using incremental load.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I see that the incremental load seems as long as the full load which is not really interesting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could it be possible to optimize this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have though about to use a BIT field instead of datetime field for the incremental load. And set an index on the field on database table I load.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The process will be something like this, for a BIT field ToLoad on a table with incremental load used:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1-all updated/inserted lines in table -&amp;gt; the field ToLoad set to 1 on the lines&lt;/P&gt;&lt;P&gt;2-QlikView application refresh with incremental condition on field "ToLoad=True"&lt;/P&gt;&lt;P&gt;3-Field ToLoad set to 0 on all the table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you think it will works better? Or any better idea?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The datetime method has truly poor performance on huge data volume as even if you set an index on a datetime field it's not really increase performance (all the value are different, the index has as values as number of table lines).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you help me?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2012 13:04:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Incremental-load-performance-low-on-big-table/m-p/391157#M698937</guid>
      <dc:creator />
      <dc:date>2012-11-29T13:04:02Z</dc:date>
    </item>
  </channel>
</rss>

