<?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: Hardware Required in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Hardware-Required/m-p/580055#M1099080</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi - just a word of caution..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you plug 10TB as a raw figure into a formula to calculate RAM needs you will most likely grossly over estimate your true RAM requirements for QLIK.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its important to&amp;nbsp; think about data requirements in terms of a limited data model not a raw database. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That doesn't come across in the documentation where we need to do a better job.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A bit more:&amp;nbsp; a single QlikView app is supported by a single data model that will cover a series of dimensions and calculate a series of KPIs. It will answer a 'family' of questions about that data model. It will give a user access to any intersection or possible summary in that data and its very easy to overload a user with information .&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are familiar with BO , Cognos or any other enterprise reporting platform a customer will likely have more than 1 data model per database to support different families of questions.&amp;nbsp; Building a giant model (in any tool) off a large database becomes harder and harder to serve all needs and ultimately becomes an exercise in compromising everything from agility to performance.&amp;nbsp; Its better and mandatory in qlikview to address a sizable chunk of data in pieces that users can manage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Qlik , for a 10TB database you will likely need more than one data model to 'package' all the information into a format that a user can actually consume. That means 'pieces' of the database for each qlikview app and sizing the pieces (probably just the first piece to begin with) and not something like&amp;nbsp; 10TB disk = 4TB RAM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i'm not saying there aren't the odd use case that needs a very deep (many rows) data set. They exist. But they aren't the norm hence my comment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 31 Oct 2014 17:36:28 GMT</pubDate>
    <dc:creator>JonnyPoole</dc:creator>
    <dc:date>2014-10-31T17:36:28Z</dc:date>
    <item>
      <title>Hardware Required</title>
      <link>https://community.qlik.com/t5/QlikView/Hardware-Required/m-p/580051#M1099074</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to know how much RAM,CPU and Storage... [HARDWARE RESOURCE] required for establish an Qlikview environment&lt;/P&gt;&lt;P&gt;for 10TB data in Oracle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rahul &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Apr 2014 08:27:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Hardware-Required/m-p/580051#M1099074</guid>
      <dc:creator />
      <dc:date>2014-04-30T08:27:26Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware Required</title>
      <link>https://community.qlik.com/t5/QlikView/Hardware-Required/m-p/580052#M1099075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check enclosed files...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Apr 2014 08:50:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Hardware-Required/m-p/580052#M1099075</guid>
      <dc:creator>MK_QSL</dc:creator>
      <dc:date>2014-04-30T08:50:45Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware Required</title>
      <link>https://community.qlik.com/t5/QlikView/Hardware-Required/m-p/580053#M1099076</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please find the attached document&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also you can refer this post&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/thread/140376"&gt;RAM&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/message/455415"&gt;Re: Calculate how much RAM needed?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 17:17:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Hardware-Required/m-p/580053#M1099076</guid>
      <dc:creator>its_anandrjs</dc:creator>
      <dc:date>2014-10-31T17:17:53Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware Required</title>
      <link>https://community.qlik.com/t5/QlikView/Hardware-Required/m-p/580054#M1099078</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;Check this too.&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-message-small" data-containerid="2057" data-containertype="14" data-objectid="455415" data-objecttype="2" href="http://community.qlik.com/message/455415#455415"&gt;http://community.qlik.com/message/455415#455415&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-message-small" data-containerid="2003" data-containertype="14" data-objectid="444168" data-objecttype="2" href="http://community.qlik.com/message/444168#444168"&gt;http://community.qlik.com/message/444168#444168&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-message-small" data-containerid="2057" data-containertype="14" data-objectid="455396" data-objecttype="2" href="http://community.qlik.com/message/455396#455396"&gt;http://community.qlik.com/message/455396#455396&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-message-small" data-containerid="2003" data-containertype="14" data-objectid="519348" data-objecttype="2" href="http://community.qlik.com/message/519348#519348"&gt;http://community.qlik.com/message/519348#519348&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;ASHFAQ&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 17:21:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Hardware-Required/m-p/580054#M1099078</guid>
      <dc:creator>ashfaq_haseeb</dc:creator>
      <dc:date>2014-10-31T17:21:01Z</dc:date>
    </item>
    <item>
      <title>Re: Hardware Required</title>
      <link>https://community.qlik.com/t5/QlikView/Hardware-Required/m-p/580055#M1099080</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi - just a word of caution..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you plug 10TB as a raw figure into a formula to calculate RAM needs you will most likely grossly over estimate your true RAM requirements for QLIK.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its important to&amp;nbsp; think about data requirements in terms of a limited data model not a raw database. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That doesn't come across in the documentation where we need to do a better job.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A bit more:&amp;nbsp; a single QlikView app is supported by a single data model that will cover a series of dimensions and calculate a series of KPIs. It will answer a 'family' of questions about that data model. It will give a user access to any intersection or possible summary in that data and its very easy to overload a user with information .&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are familiar with BO , Cognos or any other enterprise reporting platform a customer will likely have more than 1 data model per database to support different families of questions.&amp;nbsp; Building a giant model (in any tool) off a large database becomes harder and harder to serve all needs and ultimately becomes an exercise in compromising everything from agility to performance.&amp;nbsp; Its better and mandatory in qlikview to address a sizable chunk of data in pieces that users can manage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Qlik , for a 10TB database you will likely need more than one data model to 'package' all the information into a format that a user can actually consume. That means 'pieces' of the database for each qlikview app and sizing the pieces (probably just the first piece to begin with) and not something like&amp;nbsp; 10TB disk = 4TB RAM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i'm not saying there aren't the odd use case that needs a very deep (many rows) data set. They exist. But they aren't the norm hence my comment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 17:36:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Hardware-Required/m-p/580055#M1099080</guid>
      <dc:creator>JonnyPoole</dc:creator>
      <dc:date>2014-10-31T17:36:28Z</dc:date>
    </item>
  </channel>
</rss>

