<?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 Optimization of DataModel in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Optimization-of-DataModel/m-p/21253#M3529</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;I've been trying to optimize the DataModel of one app, throwing out of the LOADs a lot of fields which were beforehand deleted at the end (not needed), getting rid of a few subtables which existed only of a key and one more field and such.&lt;/P&gt;&lt;P&gt;One of the tasks involved that took a lot of time was this:&lt;/P&gt;&lt;P&gt;There were (and are still, OMG) quite a few LOADs with the * which load all the fields there are in a (SAP) table - many of these, however, were never used and thus there is a DROP FIELD statement at the end of the datamodel, dropping many of those - that was obviously generated using the DocumentAnalyzer.&lt;/P&gt;&lt;P&gt;Is there some tool that would allow me to quickly scan that DROP FIELD statement, or parts of it, and then generate a LOAD from the corresponding table not taking into account those fields? I realize that involves a few steps, so it's a bit more complex, but it seems worth having to me as I have come across the * quite a few times and I heartily dislike it ...&lt;/P&gt;&lt;P&gt;It is also recommended for loading a number of files in one go, but I had nothing but trouble with that application, too, because then the log_file won't tell you which file the error was in if there is one ..&lt;/P&gt;&lt;P&gt;Maybe it seemed worth making to anyone and someone has uploaded something to that end?&lt;/P&gt;&lt;P&gt;Thanks a lot!&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DataNibbler&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 Apr 2018 07:31:12 GMT</pubDate>
    <dc:creator>datanibbler</dc:creator>
    <dc:date>2018-04-26T07:31:12Z</dc:date>
    <item>
      <title>Optimization of DataModel</title>
      <link>https://community.qlik.com/t5/QlikView/Optimization-of-DataModel/m-p/21253#M3529</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;I've been trying to optimize the DataModel of one app, throwing out of the LOADs a lot of fields which were beforehand deleted at the end (not needed), getting rid of a few subtables which existed only of a key and one more field and such.&lt;/P&gt;&lt;P&gt;One of the tasks involved that took a lot of time was this:&lt;/P&gt;&lt;P&gt;There were (and are still, OMG) quite a few LOADs with the * which load all the fields there are in a (SAP) table - many of these, however, were never used and thus there is a DROP FIELD statement at the end of the datamodel, dropping many of those - that was obviously generated using the DocumentAnalyzer.&lt;/P&gt;&lt;P&gt;Is there some tool that would allow me to quickly scan that DROP FIELD statement, or parts of it, and then generate a LOAD from the corresponding table not taking into account those fields? I realize that involves a few steps, so it's a bit more complex, but it seems worth having to me as I have come across the * quite a few times and I heartily dislike it ...&lt;/P&gt;&lt;P&gt;It is also recommended for loading a number of files in one go, but I had nothing but trouble with that application, too, because then the log_file won't tell you which file the error was in if there is one ..&lt;/P&gt;&lt;P&gt;Maybe it seemed worth making to anyone and someone has uploaded something to that end?&lt;/P&gt;&lt;P&gt;Thanks a lot!&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DataNibbler&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2018 07:31:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Optimization-of-DataModel/m-p/21253#M3529</guid>
      <dc:creator>datanibbler</dc:creator>
      <dc:date>2018-04-26T07:31:12Z</dc:date>
    </item>
    <item>
      <title>Re: Optimization of DataModel</title>
      <link>https://community.qlik.com/t5/QlikView/Optimization-of-DataModel/m-p/21254#M3530</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In general you could load just the first record of such a table to get all included fields. Then running through those fields within a loop and comparing them with your drop-listing and excluding them. The remaining fields could be concatenated within a variable which is then used as field-list within the real load.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think you would need quite a lot of these statements to get a benefit from such a routine and by just a few of them it would be faster to copy &amp;amp; paste this stuff, applying the "text-in-columns" and the transpose feature and some lookup between them and then some sorting and filtering - all in Excel. At least someone whos is a bit experienced in Excel and knows to use the keyboard could do it in a very short time ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The last point which I understand as loading from files with a wildcard in the filename - it's often easier to use a for each filelist() loop at least if it comes to failures or other problems like different datastructures or any conditions needs to be applied ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2018 08:01:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Optimization-of-DataModel/m-p/21254#M3530</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2018-04-26T08:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: Optimization of DataModel</title>
      <link>https://community.qlik.com/t5/QlikView/Optimization-of-DataModel/m-p/21255#M3531</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Marcus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you're right - I often did this myself (replacing the * with a filelist-loop).&lt;/P&gt;&lt;P&gt;Such a routine would probably not bring me much of a saving, I guess you're right there, too.&lt;/P&gt;&lt;P&gt;I know my way around Excel reasonably well, so I could do it that way - last time I did this, however, I just generated a full listing of all fields using the hammer-symbol, added the generated fields again from a notepad and then went through the list field by field, searching the script for the fieldname and wherever I found it only in the DROP-statement, I just commented it out here and there. It might well be possible to do this faster in Excel, I will experiment a bit with that. Maybe it would even be possible to do it in Excel using a macro, that would make it even faster - and writing macros is fun, too, so I will give it a go whenever I have the time.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DataNibbler&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2018 08:08:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Optimization-of-DataModel/m-p/21255#M3531</guid>
      <dc:creator>datanibbler</dc:creator>
      <dc:date>2018-04-26T08:08:21Z</dc:date>
    </item>
  </channel>
</rss>

