<?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: Qlik Replicate Write method in Google Big query in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Write-method-in-Google-Big-query/m-p/2164268#M9027</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/213210"&gt;@harsh2&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thanks for reaching to Qlik Community!&lt;/P&gt;
&lt;P&gt;By default Qlik Replicate utilize the interim CSV files to LOAD the data (in Full Load stage, it's history data records, in CDC stage it's change data records) to Google BigQuery rather than INSERT the data rows straightly to gain better performance. Qlik Replicate composes the .CSV files (at Qlik Replicate Server) and then call LOAD command, upload the .CSV files to BigQuery storage then merge the data from interim CSV files to final target table(s).&lt;/P&gt;
&lt;P&gt;If you like you may set TARGET_LOAD &amp;amp; TARGET_APPLY to Verbose or Trace to get more information to understand the behavior further.&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;John.&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jan 2024 09:37:22 GMT</pubDate>
    <dc:creator>john_wang</dc:creator>
    <dc:date>2024-01-23T09:37:22Z</dc:date>
    <item>
      <title>Qlik Replicate Write method in Google Big query</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Write-method-in-Google-Big-query/m-p/2164252#M9025</link>
      <description>&lt;P&gt;Hi Qlik Team,&lt;/P&gt;
&lt;P&gt;I'm curious about the writing method Qlik Replicate uses in Big Query. Can you provide some insights?&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Harsh&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2024 09:22:46 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Write-method-in-Google-Big-query/m-p/2164252#M9025</guid>
      <dc:creator>harsh2</dc:creator>
      <dc:date>2024-01-23T09:22:46Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Replicate Write method in Google Big query</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Write-method-in-Google-Big-query/m-p/2164268#M9027</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/213210"&gt;@harsh2&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thanks for reaching to Qlik Community!&lt;/P&gt;
&lt;P&gt;By default Qlik Replicate utilize the interim CSV files to LOAD the data (in Full Load stage, it's history data records, in CDC stage it's change data records) to Google BigQuery rather than INSERT the data rows straightly to gain better performance. Qlik Replicate composes the .CSV files (at Qlik Replicate Server) and then call LOAD command, upload the .CSV files to BigQuery storage then merge the data from interim CSV files to final target table(s).&lt;/P&gt;
&lt;P&gt;If you like you may set TARGET_LOAD &amp;amp; TARGET_APPLY to Verbose or Trace to get more information to understand the behavior further.&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;John.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jan 2024 09:37:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-Write-method-in-Google-Big-query/m-p/2164268#M9027</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2024-01-23T09:37:22Z</dc:date>
    </item>
  </channel>
</rss>

