<?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: Best Practice for insert and updates in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Best-Practice-for-insert-and-updates/m-p/2265537#M45052</link>
    <description>&lt;BLOCKQUOTE&gt; 
 &lt;HR /&gt; 
 &lt;A href="https://community.qlik.com/s/profile/0053p000007LPHEAA4"&gt;@Vinisha&lt;/A&gt;&amp;nbsp;wrote: 
 &lt;BR /&gt; 
 &lt;P&gt;yes it worked, it improved the speed of the job , rather using insert/update inbuilt, its better to use, when we have Million&amp;nbsp; of records&lt;/P&gt; 
 &lt;HR /&gt; 
&lt;/BLOCKQUOTE&gt; 
&lt;P&gt;and it kill your Talend server when you have 100 millions&amp;nbsp;and what you will do when you have a billion?&lt;/P&gt;</description>
    <pubDate>Fri, 15 Feb 2019 05:39:22 GMT</pubDate>
    <dc:creator>vapukov</dc:creator>
    <dc:date>2019-02-15T05:39:22Z</dc:date>
    <item>
      <title>Best Practice for insert and updates</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Best-Practice-for-insert-and-updates/m-p/2265535#M45050</link>
      <description>&lt;P&gt;I have good solution for insert and updates.&amp;nbsp;&lt;BR /&gt;&lt;FONT color="#008000"&gt;(With this solution you can perform inserts and updates very very quickly)&lt;/FONT&gt;&lt;BR /&gt;When you are&amp;nbsp; getting records from the source from any data base, use tmap after any inputDb and do look up with the target , and use inner join lookup model with the cloumn to be matched, Then whatever it matches with key store all records in Temp table, Create table in the job run time.The other new which does not match with the key will go to direct insert.&amp;nbsp;&lt;BR /&gt;Than using Merge concept sync temp table and target&amp;nbsp;&lt;BR /&gt;After that delete temp table at the end&lt;BR /&gt;&lt;FONT color="#ff0000"&gt;Example of Merge query (By using this merge query it will sync source and target with in seconds)&lt;/FONT&gt;&lt;/P&gt; 
&lt;P&gt;MERGE Table A AS TARGET&lt;BR /&gt;USING Table B AS SOURCE&lt;BR /&gt;ON TARGET.tableacol1= SOURCE.col1&lt;BR /&gt;WHEN MATCHED&lt;BR /&gt;THEN&lt;BR /&gt;UPDATE&lt;BR /&gt;SET&lt;/P&gt; 
&lt;P&gt;TARGET.col2= SOURCE.col2,&lt;BR /&gt;TARGET.col3=SOURCE.col3;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Inserts-Updates-performanceimprovement.PNG" style="width: 999px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="0683p000009M381.png"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/153986i36A9C03F000E2024/image-size/large?v=v2&amp;amp;px=999" role="button" title="0683p000009M381.png" alt="0683p000009M381.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 21:12:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Best-Practice-for-insert-and-updates/m-p/2265535#M45050</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-02-14T21:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice for insert and updates</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Best-Practice-for-insert-and-updates/m-p/2265536#M45051</link>
      <description>&lt;P&gt;yes it worked, it improved the speed of the job , rather using insert/update inbuilt, its better to use, when we have Million&amp;nbsp; of records&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 21:16:33 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Best-Practice-for-insert-and-updates/m-p/2265536#M45051</guid>
      <dc:creator>Vinisha</dc:creator>
      <dc:date>2019-02-14T21:16:33Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice for insert and updates</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Best-Practice-for-insert-and-updates/m-p/2265537#M45052</link>
      <description>&lt;BLOCKQUOTE&gt; 
 &lt;HR /&gt; 
 &lt;A href="https://community.qlik.com/s/profile/0053p000007LPHEAA4"&gt;@Vinisha&lt;/A&gt;&amp;nbsp;wrote: 
 &lt;BR /&gt; 
 &lt;P&gt;yes it worked, it improved the speed of the job , rather using insert/update inbuilt, its better to use, when we have Million&amp;nbsp; of records&lt;/P&gt; 
 &lt;HR /&gt; 
&lt;/BLOCKQUOTE&gt; 
&lt;P&gt;and it kill your Talend server when you have 100 millions&amp;nbsp;and what you will do when you have a billion?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2019 05:39:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Best-Practice-for-insert-and-updates/m-p/2265537#M45052</guid>
      <dc:creator>vapukov</dc:creator>
      <dc:date>2019-02-15T05:39:22Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practice for insert and updates</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Best-Practice-for-insert-and-updates/m-p/2265538#M45053</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you please explain in more details.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2019 13:26:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Best-Practice-for-insert-and-updates/m-p/2265538#M45053</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-08-12T13:26:58Z</dc:date>
    </item>
  </channel>
</rss>

