<?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 issues with aliased fields in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Performance-issues-with-aliased-fields/m-p/379880#M141709</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 have a question regarding changes in performance (script load time) when aliasing fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I initially built a data model keeping the field names as they are in the source DB. In this scenario, when using sample data and loading 17 tables with a total of 241 fields, the load time takes 3 seconds.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I then tried to alias all the fieldnames, such as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;xx_T01:&lt;/P&gt;&lt;P&gt;Load&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Blahblah as AAA,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Blibli as AAB&lt;/P&gt;&lt;P&gt;From Source;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also tried (thinking numerical fieldnames might improve the load performance)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;xx_T01:&lt;/P&gt;&lt;P&gt;Load&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Blahblah as T01_001,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Blibli as T01_002&lt;/P&gt;&lt;P&gt;From Source;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The load in the 2 latter cases take 15 seconds (5 times more) and QV-desktop "does not respond" (hangs) for a few seconds.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When going operational this app is going to load several dozen million rows of transactional records. I expect performance will be a major issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone experienced this? Does anyone know whether there is an intelligent and BP way to do this? Out of curiosity sake, does anyone know why QV responds in this way (e.g. closeness in naming of fields/dims)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks for your help and thoughts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheenu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 Aug 2012 13:02:38 GMT</pubDate>
    <dc:creator />
    <dc:date>2012-08-22T13:02:38Z</dc:date>
    <item>
      <title>Performance issues with aliased fields</title>
      <link>https://community.qlik.com/t5/QlikView/Performance-issues-with-aliased-fields/m-p/379880#M141709</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 have a question regarding changes in performance (script load time) when aliasing fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I initially built a data model keeping the field names as they are in the source DB. In this scenario, when using sample data and loading 17 tables with a total of 241 fields, the load time takes 3 seconds.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I then tried to alias all the fieldnames, such as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;xx_T01:&lt;/P&gt;&lt;P&gt;Load&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Blahblah as AAA,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Blibli as AAB&lt;/P&gt;&lt;P&gt;From Source;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also tried (thinking numerical fieldnames might improve the load performance)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;xx_T01:&lt;/P&gt;&lt;P&gt;Load&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Blahblah as T01_001,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Blibli as T01_002&lt;/P&gt;&lt;P&gt;From Source;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The load in the 2 latter cases take 15 seconds (5 times more) and QV-desktop "does not respond" (hangs) for a few seconds.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When going operational this app is going to load several dozen million rows of transactional records. I expect performance will be a major issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone experienced this? Does anyone know whether there is an intelligent and BP way to do this? Out of curiosity sake, does anyone know why QV responds in this way (e.g. closeness in naming of fields/dims)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks for your help and thoughts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheenu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Aug 2012 13:02:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Performance-issues-with-aliased-fields/m-p/379880#M141709</guid>
      <dc:creator />
      <dc:date>2012-08-22T13:02:38Z</dc:date>
    </item>
  </channel>
</rss>

