<?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: Large table and document chaining in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Large-table-and-document-chaining/m-p/74469#M12265</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think a document chaining won't have a real positive effect because quite likely there are always some users which are not just looking on the aggregated app else they will go to the chained detail-app and therefore you will get two apps which are handled in parallel from the server. It will need more resources than a single app.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Jun 2018 11:17:31 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2018-06-25T11:17:31Z</dc:date>
    <item>
      <title>Large table and document chaining</title>
      <link>https://community.qlik.com/t5/QlikView/Large-table-and-document-chaining/m-p/74468#M12264</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 was wondering what would the difference in performance for the following two scenarios&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;app with 10 millions rows&amp;nbsp; by 500 users&amp;nbsp; an&lt;/LI&gt;&lt;LI&gt;aggregate app to 200,000 row&amp;nbsp; but when making a selection on chart would lead to that same 10 millions app but opening it using document chaining for a particular selection, this scenario will e used by 500 users&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;which of the above scenarios is most optimal&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;many thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jun 2018 10:13:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Large-table-and-document-chaining/m-p/74468#M12264</guid>
      <dc:creator>mbrm_218</dc:creator>
      <dc:date>2018-06-25T10:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: Large table and document chaining</title>
      <link>https://community.qlik.com/t5/QlikView/Large-table-and-document-chaining/m-p/74469#M12265</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think a document chaining won't have a real positive effect because quite likely there are always some users which are not just looking on the aggregated app else they will go to the chained detail-app and therefore you will get two apps which are handled in parallel from the server. It will need more resources than a single app.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jun 2018 11:17:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Large-table-and-document-chaining/m-p/74469#M12265</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2018-06-25T11:17:31Z</dc:date>
    </item>
  </channel>
</rss>

