<?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: how to improve the perfomance ? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/how-to-improve-the-perfomance/m-p/763930#M1022514</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Generically:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;Simplify Data Model - if possible no Synthetic Keys.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Avoid ODBC. OLEDB has more performance.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;Simplify SQL &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;Tunning SQL.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reduce data (remove columns unnecessary).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Split Timestamp fields in Data and Time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Simplify Design Model - Avoid use of images.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Minimize number of Triggers &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Test Macro code if used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Avoid use of peek.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use Set Analysis.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;............................................&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 22 Mar 2015 14:45:51 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2015-03-22T14:45:51Z</dc:date>
    <item>
      <title>how to improve the perfomance ?</title>
      <link>https://community.qlik.com/t5/QlikView/how-to-improve-the-perfomance/m-p/763927#M1022511</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;how to improve the perfomance ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Mar 2015 14:55:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/how-to-improve-the-perfomance/m-p/763927#M1022511</guid>
      <dc:creator />
      <dc:date>2015-03-21T14:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: how to improve the perfomance ?</title>
      <link>https://community.qlik.com/t5/QlikView/how-to-improve-the-perfomance/m-p/763928#M1022512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is a very open question, to solicit a sensible answer you need to be specific as to what your issue is.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Mar 2015 15:04:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/how-to-improve-the-perfomance/m-p/763928#M1022512</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-03-21T15:04:28Z</dc:date>
    </item>
    <item>
      <title>Re: how to improve the perfomance ?</title>
      <link>https://community.qlik.com/t5/QlikView/how-to-improve-the-perfomance/m-p/763929#M1022513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You're right Bill &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have to provide a bit more information.. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. The first thing to check is the way you have created your keys, the links between tables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Reconsider no. 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. &lt;/P&gt;&lt;P&gt;How many records are there?&lt;/P&gt;&lt;P&gt;Show us your data structure (Ctrl-T in Qlikview).&lt;/P&gt;&lt;P&gt;Do you have synthetic keys in your structure?&lt;/P&gt;&lt;P&gt;Perhaps there are too many or too few hubs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a look at &lt;/P&gt;&lt;P&gt;Settings (menu) &amp;gt; Document properties &amp;gt; Tables &amp;gt; Fields (below)&lt;/P&gt;&lt;P&gt;Reconsider fields with big numbers of #Distinct. &lt;/P&gt;&lt;P&gt;Do you really need these fields? &lt;/P&gt;&lt;P&gt;If not, drop them ath the end of your script:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DROP FIELD x;&lt;/P&gt;&lt;P&gt;or DROP FIELDS A, B, C;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Grtz Fred&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Mar 2015 15:14:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/how-to-improve-the-perfomance/m-p/763929#M1022513</guid>
      <dc:creator>fred_s</dc:creator>
      <dc:date>2015-03-21T15:14:53Z</dc:date>
    </item>
    <item>
      <title>Re: how to improve the perfomance ?</title>
      <link>https://community.qlik.com/t5/QlikView/how-to-improve-the-perfomance/m-p/763930#M1022514</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Generically:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;Simplify Data Model - if possible no Synthetic Keys.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Avoid ODBC. OLEDB has more performance.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;Simplify SQL &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;Tunning SQL.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reduce data (remove columns unnecessary).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Split Timestamp fields in Data and Time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Simplify Design Model - Avoid use of images.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Minimize number of Triggers &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Test Macro code if used.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Avoid use of peek.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use Set Analysis.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;............................................&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 22 Mar 2015 14:45:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/how-to-improve-the-perfomance/m-p/763930#M1022514</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-03-22T14:45:51Z</dc:date>
    </item>
    <item>
      <title>Re: how to improve the perfomance ?</title>
      <link>https://community.qlik.com/t5/QlikView/how-to-improve-the-perfomance/m-p/763931#M1022515</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1) first we can check any synthtic keys and circulr loop is there .then we can avoid things&lt;/P&gt;&lt;P&gt;join,concatnate,alias after that&lt;SPAN lang="EN" style="font-size: 10.0pt; font-family: 'Helvetica','sans-serif'; color: #3d3d3d;"&gt;In addition to that, using set analysis and removing unused fields from the application is also would improve the performance of the application.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-size: 11.0pt; font-family: 'Calibri','sans-serif';"&gt;If i didn’t use any tables means i vl drop the unnecessary tables&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Mar 2015 04:39:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/how-to-improve-the-perfomance/m-p/763931#M1022515</guid>
      <dc:creator />
      <dc:date>2015-03-23T04:39:39Z</dc:date>
    </item>
  </channel>
</rss>

