<?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: Upgrading RAM on physical server in Connectivity &amp; Data Prep</title>
    <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Upgrading-RAM-on-physical-server/m-p/28040#M196</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Very unlikely. He could however use QVD-files to have a staging layer for the data and that can siginificantly speed up the reload process - up to 20 times the speed when it comes to relation databases and probably more with Salesforce.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 May 2018 20:27:03 GMT</pubDate>
    <dc:creator>petter</dc:creator>
    <dc:date>2018-05-14T20:27:03Z</dc:date>
    <item>
      <title>Upgrading RAM on physical server</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Upgrading-RAM-on-physical-server/m-p/28039#M195</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Our BI resource has brought to our attention that when creating an app within Qlicksense he must load a heavy amount of data from our Salesforce environment.&amp;nbsp; At times this data load can take anywhere from 5 to 20 minutes.&amp;nbsp; Each time he makes changes to the code he must perform another load.&amp;nbsp; He's spending a lot of time waiting for the data load.&amp;nbsp; Currently our server has 16GB of RAM.&amp;nbsp; Would upgrading the RAM have a significant improvement on his data load times?&amp;nbsp; Thanks in advance for any suggestions.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2018 13:36:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/Upgrading-RAM-on-physical-server/m-p/28039#M195</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-05-14T13:36:15Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading RAM on physical server</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Upgrading-RAM-on-physical-server/m-p/28040#M196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Very unlikely. He could however use QVD-files to have a staging layer for the data and that can siginificantly speed up the reload process - up to 20 times the speed when it comes to relation databases and probably more with Salesforce.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2018 20:27:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/Upgrading-RAM-on-physical-server/m-p/28040#M196</guid>
      <dc:creator>petter</dc:creator>
      <dc:date>2018-05-14T20:27:03Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading RAM on physical server</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Upgrading-RAM-on-physical-server/m-p/28041#M197</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Another option that can be used is the BUFFER prefix for the LOAD statement that will buffer/cache the content from Salesforce automatically.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a look here: &lt;A href="https://help.qlik.com/en-US/sense/April2018/Subsystems/Hub/Content/Scripting/ScriptPrefixes/Buffer.htm" title="https://help.qlik.com/en-US/sense/April2018/Subsystems/Hub/Content/Scripting/ScriptPrefixes/Buffer.htm"&gt;https://help.qlik.com/en-US/sense/April2018/Subsystems/Hub/Content/Scripting/ScriptPrefixes/Buffer.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2018 20:29:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/Upgrading-RAM-on-physical-server/m-p/28041#M197</guid>
      <dc:creator>petter</dc:creator>
      <dc:date>2018-05-14T20:29:04Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading RAM on physical server</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Upgrading-RAM-on-physical-server/m-p/28042#M198</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How does buffer know which field is the timestamp field?&amp;nbsp; And is 'Buffer' another way of doing an incremental load, cause that's what it looks like.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 May 2018 20:43:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/Upgrading-RAM-on-physical-server/m-p/28042#M198</guid>
      <dc:creator>JustinDallas</dc:creator>
      <dc:date>2018-05-15T20:43:59Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading RAM on physical server</title>
      <link>https://community.qlik.com/t5/Connectivity-Data-Prep/Upgrading-RAM-on-physical-server/m-p/28043#M199</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Buffer is a cache mechanism so you can specify the update frequency. It will not use any timestamp field - it is not an alternative to incremental load. It makes you less dependent on reading the source and speeds up the development significantly. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 May 2018 09:35:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Connectivity-Data-Prep/Upgrading-RAM-on-physical-server/m-p/28043#M199</guid>
      <dc:creator>petter</dc:creator>
      <dc:date>2018-05-16T09:35:29Z</dc:date>
    </item>
  </channel>
</rss>

