<?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 Performance Issue...Share your Experience! in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Performance-Issue-Share-your-Experience/m-p/367848#M136803</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Salman,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd say there is no best answer for this. In regards to formats, it all depends on how many functions do you need to apply to the files in order to clean them up and get the data properly to make further analyses with it. It seems that all of them are plain text files, and all of them should perform quite the same in QlikView.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In regards to the RDBM again, it depends on your driver, how the server is configured, 32 or 64 bit architecture...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, I'd say: whenever possible, use QVDs. Of course you will need to pull data before using them, but once you do a LOAD, do a STORE into QVD files. These are, by far, (and with the possible exception of binary loads) the fastest way to load data into QlikView. Check the Partner Portal and the QlikCommunity about "three tier" architecture, that is, roughly speaking, using one file to pull raw data from data sources and store it into QVD files, a second file pulling from QVDs and creating the data model, and a third one that has all design and layout elements and pulls data from the second file by means of a binary load (super fast as well).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that makes sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Miguel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Apr 2012 13:26:05 GMT</pubDate>
    <dc:creator>Miguel_Angel_Baeyens</dc:creator>
    <dc:date>2012-04-25T13:26:05Z</dc:date>
    <item>
      <title>Performance Issue...Share your Experience!</title>
      <link>https://community.qlik.com/t5/QlikView/Performance-Issue-Share-your-Experience/m-p/367847#M136802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello Everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to ask which type of data source files work&amp;nbsp; best with QlikView....for example we have a choice to have our source files in different file formats like &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1-.bin&lt;/P&gt;&lt;P&gt;2-.csv &lt;/P&gt;&lt;P&gt;3-.sql &lt;/P&gt;&lt;P&gt;4-.log &lt;/P&gt;&lt;P&gt;5-.txt&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;which format is best for data source in terms of&amp;nbsp; performance.?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And if Relational DataBase like MySQL&amp;nbsp; works best with QlikView? or we should use NoSql? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Share your experience please.&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;Salman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Apr 2012 13:12:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Performance-Issue-Share-your-Experience/m-p/367847#M136802</guid>
      <dc:creator />
      <dc:date>2012-04-25T13:12:26Z</dc:date>
    </item>
    <item>
      <title>Performance Issue...Share your Experience!</title>
      <link>https://community.qlik.com/t5/QlikView/Performance-Issue-Share-your-Experience/m-p/367848#M136803</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Salman,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd say there is no best answer for this. In regards to formats, it all depends on how many functions do you need to apply to the files in order to clean them up and get the data properly to make further analyses with it. It seems that all of them are plain text files, and all of them should perform quite the same in QlikView.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In regards to the RDBM again, it depends on your driver, how the server is configured, 32 or 64 bit architecture...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, I'd say: whenever possible, use QVDs. Of course you will need to pull data before using them, but once you do a LOAD, do a STORE into QVD files. These are, by far, (and with the possible exception of binary loads) the fastest way to load data into QlikView. Check the Partner Portal and the QlikCommunity about "three tier" architecture, that is, roughly speaking, using one file to pull raw data from data sources and store it into QVD files, a second file pulling from QVDs and creating the data model, and a third one that has all design and layout elements and pulls data from the second file by means of a binary load (super fast as well).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that makes sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Miguel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Apr 2012 13:26:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Performance-Issue-Share-your-Experience/m-p/367848#M136803</guid>
      <dc:creator>Miguel_Angel_Baeyens</dc:creator>
      <dc:date>2012-04-25T13:26:05Z</dc:date>
    </item>
    <item>
      <title>Performance Issue...Share your Experience!</title>
      <link>https://community.qlik.com/t5/QlikView/Performance-Issue-Share-your-Experience/m-p/367849#M136804</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks Miguel &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Apr 2012 13:45:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Performance-Issue-Share-your-Experience/m-p/367849#M136804</guid>
      <dc:creator />
      <dc:date>2012-04-25T13:45:11Z</dc:date>
    </item>
  </channel>
</rss>

