<?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: Merge 2 data models in single qvw in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Merge-2-data-models-in-single-qvw/m-p/1247364#M395316</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think that you will get any performance improvements from splitting a datamodel but keeping them as two separate datamodels within a single qvw - rather the opposite. The splitting itself will give you performance advantages if you then used two or even more qvw's - and you might use some simple kind of document chaining to enable the users to switch from one to another.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Beside this there might be further possibilities to improve the application performance by only loading needed fields and removing such things like record-ID's, splitting timestamps and of course avoiding aggr-functions and nested if-loops within the UI could speed up an application significantly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Mar 2017 09:14:31 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2017-03-21T09:14:31Z</dc:date>
    <item>
      <title>Merge 2 data models in single qvw</title>
      <link>https://community.qlik.com/t5/QlikView/Merge-2-data-models-in-single-qvw/m-p/1247363#M395315</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Friends , &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have one situation where i have 200 million records since 2014 ,and i have created one data model using the fact and some dimension tables , now i am planing to split that data model into 2 part because it is taking lot of time , &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Previews Model&lt;/P&gt;&lt;P&gt;Current Year Model&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that i want to concat both qvw data in single qvw . everything will work fine but my dimension table data is getting duplicate. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to avoid this situation , is there any solution for this or please suggest some other ways also.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Mar 2017 06:41:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Merge-2-data-models-in-single-qvw/m-p/1247363#M395315</guid>
      <dc:creator>agni_gold</dc:creator>
      <dc:date>2017-03-21T06:41:12Z</dc:date>
    </item>
    <item>
      <title>Re: Merge 2 data models in single qvw</title>
      <link>https://community.qlik.com/t5/QlikView/Merge-2-data-models-in-single-qvw/m-p/1247364#M395316</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think that you will get any performance improvements from splitting a datamodel but keeping them as two separate datamodels within a single qvw - rather the opposite. The splitting itself will give you performance advantages if you then used two or even more qvw's - and you might use some simple kind of document chaining to enable the users to switch from one to another.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Beside this there might be further possibilities to improve the application performance by only loading needed fields and removing such things like record-ID's, splitting timestamps and of course avoiding aggr-functions and nested if-loops within the UI could speed up an application significantly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Mar 2017 09:14:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Merge-2-data-models-in-single-qvw/m-p/1247364#M395316</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2017-03-21T09:14:31Z</dc:date>
    </item>
  </channel>
</rss>

