<?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! in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/performance-issue/m-p/191544#M53593</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Obviously the problem is not about slow data load, but about run-time performance. The issues could be related to :&lt;BR /&gt;1. Too much data&lt;BR /&gt;2. Ineffective data model.&lt;BR /&gt;3. Too complex chart calculations&lt;BR /&gt;4. Macro is running too long.&lt;BR /&gt;Or it could be combination of several factors. Each require different solutions, so the first step will be to find out what's going on.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 19 Jun 2010 16:44:52 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2010-06-19T16:44:52Z</dc:date>
    <item>
      <title>performance issue!</title>
      <link>https://community.qlik.com/t5/QlikView/performance-issue/m-p/191540#M53589</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;my client is having many unrequired data fields because of which it is taking a long time to reload. keeping this problem in mind i have commented those unrequired fields but still the performance of that qlikview application hasn't improved.&lt;/P&gt;&lt;P&gt;what should i do next? does wrong data modelling also affects the performance? if you answer 'yes then i shall be removing some tables...? kindly help!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 06:22:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/performance-issue/m-p/191540#M53589</guid>
      <dc:creator />
      <dc:date>2010-06-17T06:22:45Z</dc:date>
    </item>
    <item>
      <title>performance issue!</title>
      <link>https://community.qlik.com/t5/QlikView/performance-issue/m-p/191541#M53590</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Keep in mind that commenting out fields from the LOAD statement does not make any difference to what is actually transferred from the database server - it only reduces the size of the data model in QV.&lt;/P&gt;&lt;P&gt;(I am assuming that you load from database tables, not from files.)&lt;/P&gt;&lt;P&gt;It is unfortunately fairly common to use SELECT * in the Select-statement in QV. This is contrary to best practice in database development, and has been since relational databases became common.Best practice is to list exactly the columns that you want - even if that includes all columns currently in the source table.&lt;/P&gt;&lt;P&gt;Also, I sometimes see scripts where the WHERE condition is in the LOAD statement, not in the SELECT statement. This means that the complete table has to be loaded to the QV server, and then only some of the rows will be loaded into QV.&lt;/P&gt;&lt;P&gt;So, if your performance issues are related to the amount of data transferred across the network: Try to replace SELECT * with SELECT &amp;lt;column-name-list&amp;gt;, and move any WHERE conditions from LOAD-statement to SELECT-statement.&lt;/P&gt;&lt;P&gt;Best regards, Vegard.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jun 2010 07:00:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/performance-issue/m-p/191541#M53590</guid>
      <dc:creator />
      <dc:date>2010-06-17T07:00:43Z</dc:date>
    </item>
    <item>
      <title>performance issue!</title>
      <link>https://community.qlik.com/t5/QlikView/performance-issue/m-p/191542#M53591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi vegard,&lt;/P&gt;&lt;P&gt;thanks for the help. actually what is happening that one of the sheet in qvw is taking a long time to open. as said earlier i was commenting the fields but it didn't made any noticeable difference. what should be the next easy step to that i should do. because the client for which i m working for wants the application to be done within 2 days of time. further on changing the data modeling will make the task longer as it will require more time and resources.&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;gaurav&lt;/P&gt;&lt;P&gt;consultant-bi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Jun 2010 06:10:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/performance-issue/m-p/191542#M53591</guid>
      <dc:creator />
      <dc:date>2010-06-19T06:10:06Z</dc:date>
    </item>
    <item>
      <title>performance issue!</title>
      <link>https://community.qlik.com/t5/QlikView/performance-issue/m-p/191543#M53592</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Gaurav,&lt;/P&gt;&lt;P&gt;Please specify you are fetching data from which data source. its oracle , Sap or some other.???&lt;/P&gt;&lt;P&gt;and you are selecting all the tables fileds or some restrictions are made..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ashwin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Jun 2010 10:59:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/performance-issue/m-p/191543#M53592</guid>
      <dc:creator />
      <dc:date>2010-06-19T10:59:11Z</dc:date>
    </item>
    <item>
      <title>performance issue!</title>
      <link>https://community.qlik.com/t5/QlikView/performance-issue/m-p/191544#M53593</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Obviously the problem is not about slow data load, but about run-time performance. The issues could be related to :&lt;BR /&gt;1. Too much data&lt;BR /&gt;2. Ineffective data model.&lt;BR /&gt;3. Too complex chart calculations&lt;BR /&gt;4. Macro is running too long.&lt;BR /&gt;Or it could be combination of several factors. Each require different solutions, so the first step will be to find out what's going on.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Jun 2010 16:44:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/performance-issue/m-p/191544#M53593</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-06-19T16:44:52Z</dc:date>
    </item>
  </channel>
</rss>

