<?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 how to ingest large SAP tables in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/how-to-ingest-large-SAP-tables/m-p/2325833#M95383</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt; 
&lt;P&gt;we have SAP BW objects that contain several 100ks of rows with over 100 fields. We get out of memory exceptions, so increased the memory for the job to 8GB.&lt;/P&gt; 
&lt;P&gt;However some (very important) tables, have millions of rows and still require more memory (simple calculation tells us &amp;gt;30 GB required). For other components I saw similar posts saying you can enable stream data, but it seems that for the components we used (tSAPADSOInput/TSAPInfoObject). THe question is: is Talend not capable of ingesting this amount of data? If it always loads everything into memory, before writing it, this is a major limitation.&lt;/P&gt; 
&lt;P&gt;A solution would be to select only a part of the data, but it also seems not to be possible to define a query in the style 'SELECT * FROM table where date&amp;gt; ' for our components. I feel like&amp;nbsp;that a product like Talend should have a workaround, but I might not have encountered it yet.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Thanks for input!!&lt;/P&gt;</description>
    <pubDate>Fri, 29 Jun 2018 11:37:09 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2018-06-29T11:37:09Z</dc:date>
    <item>
      <title>how to ingest large SAP tables</title>
      <link>https://community.qlik.com/t5/Talend-Studio/how-to-ingest-large-SAP-tables/m-p/2325833#M95383</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt; 
&lt;P&gt;we have SAP BW objects that contain several 100ks of rows with over 100 fields. We get out of memory exceptions, so increased the memory for the job to 8GB.&lt;/P&gt; 
&lt;P&gt;However some (very important) tables, have millions of rows and still require more memory (simple calculation tells us &amp;gt;30 GB required). For other components I saw similar posts saying you can enable stream data, but it seems that for the components we used (tSAPADSOInput/TSAPInfoObject). THe question is: is Talend not capable of ingesting this amount of data? If it always loads everything into memory, before writing it, this is a major limitation.&lt;/P&gt; 
&lt;P&gt;A solution would be to select only a part of the data, but it also seems not to be possible to define a query in the style 'SELECT * FROM table where date&amp;gt; ' for our components. I feel like&amp;nbsp;that a product like Talend should have a workaround, but I might not have encountered it yet.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Thanks for input!!&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jun 2018 11:37:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/how-to-ingest-large-SAP-tables/m-p/2325833#M95383</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-06-29T11:37:09Z</dc:date>
    </item>
    <item>
      <title>Re: how to ingest large SAP tables</title>
      <link>https://community.qlik.com/t5/Talend-Studio/how-to-ingest-large-SAP-tables/m-p/2325834#M95384</link>
      <description>&lt;P&gt;Count the amount, Use/create rownumber.&lt;BR /&gt;Or&lt;BR /&gt;Use an id which has a number.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;next is iteration. 350k records, calculate size, of n records (maximize)&lt;BR /&gt;Every iteration, say, you take 25k records: 1-25, 25-50k, etc.&lt;BR /&gt;&lt;BR /&gt;Note:&lt;BR /&gt;- Avoid using tMap, store directly into file or whatever, if possible.&lt;BR /&gt;- Minimize your extracted string size because that consumes memory.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt; 
&lt;P&gt;You could maybe use a different connection approach: because SAP&amp;nbsp;run on top of database engines:&amp;nbsp;most common ones :&amp;nbsp;&lt;SPAN&gt;DB2, MS SQL, Oracle&amp;nbsp;or HANA&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Jul 2018 17:21:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/how-to-ingest-large-SAP-tables/m-p/2325834#M95384</guid>
      <dc:creator>Jesperrekuh</dc:creator>
      <dc:date>2018-07-02T17:21:49Z</dc:date>
    </item>
  </channel>
</rss>

