<?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 3 tier or 4 tier ? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/3-tier-or-4-tier/m-p/59539#M9883</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At present&amp;nbsp; 2 tier architecture is implemented&amp;nbsp; in our dashboard .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we are trying to make it as 3 tier like&lt;/P&gt;&lt;P&gt;1)Extract(Incremental load )&lt;/P&gt;&lt;P&gt;2)DataModel( Load qvds and then do transformations (like joins,applymap,concatenations) based on Requirement )&lt;/P&gt;&lt;P&gt;3)Binary load .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently the dashboard size is 8 GB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;currently the qvds that are required for this dashboard are around 40 qvds.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the qvds size is 22 GB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought of 4 tier approach where in we will do all the transformation logic in 2nd layer using the base qvds(Extract layer)&amp;nbsp; and in DataModel layer , load &lt;SPAN style="font-size: 13.3333px;"&gt;only&amp;nbsp; &lt;/SPAN&gt;transformed QVDS which will be of OPTIMIZED LOADS.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;But this approach will make the duplication of qvds or Creation of additional qvds&amp;nbsp; which may go around 15 GB.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what could be the best way to approach ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Mar 2018 14:47:04 GMT</pubDate>
    <dc:creator>veeranj</dc:creator>
    <dc:date>2018-03-06T14:47:04Z</dc:date>
    <item>
      <title>3 tier or 4 tier ?</title>
      <link>https://community.qlik.com/t5/QlikView/3-tier-or-4-tier/m-p/59539#M9883</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At present&amp;nbsp; 2 tier architecture is implemented&amp;nbsp; in our dashboard .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we are trying to make it as 3 tier like&lt;/P&gt;&lt;P&gt;1)Extract(Incremental load )&lt;/P&gt;&lt;P&gt;2)DataModel( Load qvds and then do transformations (like joins,applymap,concatenations) based on Requirement )&lt;/P&gt;&lt;P&gt;3)Binary load .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently the dashboard size is 8 GB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;currently the qvds that are required for this dashboard are around 40 qvds.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the qvds size is 22 GB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought of 4 tier approach where in we will do all the transformation logic in 2nd layer using the base qvds(Extract layer)&amp;nbsp; and in DataModel layer , load &lt;SPAN style="font-size: 13.3333px;"&gt;only&amp;nbsp; &lt;/SPAN&gt;transformed QVDS which will be of OPTIMIZED LOADS.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;But this approach will make the duplication of qvds or Creation of additional qvds&amp;nbsp; which may go around 15 GB.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what could be the best way to approach ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Mar 2018 14:47:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/3-tier-or-4-tier/m-p/59539#M9883</guid>
      <dc:creator>veeranj</dc:creator>
      <dc:date>2018-03-06T14:47:04Z</dc:date>
    </item>
  </channel>
</rss>

