<?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: Incremental load in raw query in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Incremental-load-in-raw-query/m-p/1740509#M56685</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/72298"&gt;@iswarya&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's a strange format for database data to be in. If it is the case though, you need to use&amp;nbsp;&lt;STRONG&gt;subfield&lt;/STRONG&gt; to get all of the parts out.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;LOAD
    subfield(Column1, ',', 1) as ID,
    subfield(Column1, ',', 2) as Name,
etc.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The problem that you will have though is that a WHERE statement in the SQL is likely to be inefficient anyway as the fields will not be properly indexed.&lt;/P&gt;&lt;P&gt;For general incremental load help, you may want to look &lt;A href="https://www.quickintelligence.co.uk/qlikview-incremental-load/" target="_self"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;</description>
    <pubDate>Wed, 02 Sep 2020 06:59:33 GMT</pubDate>
    <dc:creator>stevedark</dc:creator>
    <dc:date>2020-09-02T06:59:33Z</dc:date>
    <item>
      <title>Incremental load in raw query</title>
      <link>https://community.qlik.com/t5/App-Development/Incremental-load-in-raw-query/m-p/1740501#M56684</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am using&amp;nbsp;postgresql. I want to do a incremental load in qlik. But the issue here is, all the columns(ID,Name) are stored in a single column as Column1 in the raw query.&amp;nbsp;&lt;/P&gt;&lt;P&gt;After a full load, need to implement multiple transformation to get the fields(ID,Name) and then store it as final qvd.&lt;/P&gt;&lt;P&gt;How to achieve the incremental load for data like this?&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2020 06:47:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Incremental-load-in-raw-query/m-p/1740501#M56684</guid>
      <dc:creator>iswarya</dc:creator>
      <dc:date>2020-09-02T06:47:01Z</dc:date>
    </item>
    <item>
      <title>Re: Incremental load in raw query</title>
      <link>https://community.qlik.com/t5/App-Development/Incremental-load-in-raw-query/m-p/1740509#M56685</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/72298"&gt;@iswarya&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That's a strange format for database data to be in. If it is the case though, you need to use&amp;nbsp;&lt;STRONG&gt;subfield&lt;/STRONG&gt; to get all of the parts out.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;LOAD
    subfield(Column1, ',', 1) as ID,
    subfield(Column1, ',', 2) as Name,
etc.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The problem that you will have though is that a WHERE statement in the SQL is likely to be inefficient anyway as the fields will not be properly indexed.&lt;/P&gt;&lt;P&gt;For general incremental load help, you may want to look &lt;A href="https://www.quickintelligence.co.uk/qlikview-incremental-load/" target="_self"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2020 06:59:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Incremental-load-in-raw-query/m-p/1740509#M56685</guid>
      <dc:creator>stevedark</dc:creator>
      <dc:date>2020-09-02T06:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: Incremental load in raw query</title>
      <link>https://community.qlik.com/t5/App-Development/Incremental-load-in-raw-query/m-p/1740917#M56724</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/6748"&gt;@stevedark&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I need to implement incremental load in the query.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2020 08:15:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Incremental-load-in-raw-query/m-p/1740917#M56724</guid>
      <dc:creator>iswarya</dc:creator>
      <dc:date>2020-09-03T08:15:02Z</dc:date>
    </item>
    <item>
      <title>Re: Incremental load in raw query</title>
      <link>https://community.qlik.com/t5/App-Development/Incremental-load-in-raw-query/m-p/1740926#M56727</link>
      <description>&lt;P&gt;If the database needs to do a full table scan, due to not having an index, it will take as long to pull the last day or so of data as it will the whole table. In this case an incremental load will not be of any use.&lt;/P&gt;&lt;P&gt;Is it that the data in the database is cleared down so that you need to persist old data to QVD?&lt;/P&gt;&lt;P&gt;The article I posted a link to above has lots on information on incremental loads. There are many ways of achieving them and the best for you will depend on your requirements.&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2020 09:20:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Incremental-load-in-raw-query/m-p/1740926#M56727</guid>
      <dc:creator>stevedark</dc:creator>
      <dc:date>2020-09-03T09:20:30Z</dc:date>
    </item>
    <item>
      <title>Re: Incremental load in raw query</title>
      <link>https://community.qlik.com/t5/App-Development/Incremental-load-in-raw-query/m-p/1741074#M56742</link>
      <description>&lt;P&gt;Yes, I need to persist old data to QVD.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2020 17:23:41 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Incremental-load-in-raw-query/m-p/1741074#M56742</guid>
      <dc:creator>iswarya</dc:creator>
      <dc:date>2020-09-03T17:23:41Z</dc:date>
    </item>
  </channel>
</rss>

