<?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>article Qlik Google BigQuery Connector: How to setup load from Large Datasets in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Google-BigQuery-Connector-How-to-setup-load-from-Large/ta-p/1937223</link>
    <description>&lt;P&gt;Google BigQuery limits cached results to approximately 10 GB compressed. Queries that return larger results overtake this limit and frequently result in the following error:&amp;nbsp;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;Response too large to return. Consider setting allowLargeResults to true in your job configuration&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H4&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Environment:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H4&gt;&lt;UL&gt;&lt;LI&gt;Qlik Google BigQuery Connector (Qlik Cloud)&lt;/LI&gt;&lt;LI&gt;Qlik Google BigQuery Connector (Qlik Sense Enterprise on Windows August 2021 and later)&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;&amp;nbsp;&lt;/H3&gt;&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Resolution&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H3&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To mitigate the "Response too large" error, you will have to set the queries to run with the Destination dataset specified&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;In Standard SQL, specify a destination table for the query results.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;In Legacy SQL, specify a destination table and set the allowLargeResults option.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Step by Step guide:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Create a destination dataset under your GBQ project&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image2022-5-30_15-45-24.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/80621iF19797EB3EC43965/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image2022-5-30_15-45-24.png" alt="image2022-5-30_15-45-24.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Make sure to set "Table expiration settings" for this dataset, as the temporary tables created by the driver will inherit the settings from the parent dataset.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image2022-5-30_15-46-57.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/80622i0205D1DF99D2594E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image2022-5-30_15-46-57.png" alt="image2022-5-30_15-46-57.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;Configure Qlik Google big query connector with the below settings&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;OL&gt;&lt;LI&gt;For Standard SQL, just provide the dataset name as shown below&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image2022-5-30_16-4-23.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/80624iF95BF9AFE036A1AF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image2022-5-30_16-4-23.png" alt="image2022-5-30_16-4-23.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;For Legacy SQL,&amp;nbsp; Select Legacy SQL from language Dilect, then enable Allow Large Result Sets checkbox and provide the dataset name as shown below&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image2022-5-30_16-8-41.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/80625i73408BEB44A1AF7A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image2022-5-30_16-8-41.png" alt="image2022-5-30_16-8-41.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;&lt;FONT size="3"&gt;Performance considerations:&lt;/FONT&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;As rightly quoted&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://cloud.google.com/bigquery/docs/best-practices-performance-output" target="_blank" rel="nofollow noopener"&gt;here&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;"&lt;SPAN&gt;Be aware that writing very large result sets to destination tables impacts query performance (I/O)", enabling large datasets settings will impact query performance and might slow down reloads.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So, to improve performance while working with destination tables strategy, its advisable to enable high throughput API&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image2022-5-30_16-54-15.png" style="width: 275px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/80626i69C05935E82D5B77/image-size/large?v=v2&amp;amp;px=999" role="button" title="image2022-5-30_16-54-15.png" alt="image2022-5-30_16-54-15.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Performance can be further be increased by using the alternate processing method for optimization reload by enabling Bulk Reader checkbox&amp;nbsp; (as shown in the screenshot above)&lt;/P&gt;&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;&lt;H4&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Related Content:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H4&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Google BigQuery Docs: Writing large data results&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;A href="https://cloud.google.com/bigquery/docs/writing-results#large-results" target="_blank" rel="nofollow noopener"&gt;https://cloud.google.com/bigquery/docs/writing-results#large-results&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Google BigQuery Docs:&amp;nbsp;Manage query outputs &lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="https://cloud.google.com/bigquery/docs/best-practices-performance-output" target="_blank" rel="nofollow noopener"&gt;https://cloud.google.com/bigquery/docs/best-practices-performance-output&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;Qlik Cloud Help: Google BigQuery Connector load optimization settings&lt;BR /&gt;&lt;A href="https://help.qlik.com/en-US/connectors/Subsystems/ODBC_connector_help/Content/Connectors_ODBC/GoogleBigQuery/Create-GBQ-Connection.htm#anchor-8" target="_blank" rel="noopener"&gt;https://help.qlik.com/en-US/connectors/Subsystems/ODBC_connector_help/Content/Connectors_ODBC/GoogleBigQuery/Create-GBQ-Connection.htm#anchor-8&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Jun 2022 08:09:37 GMT</pubDate>
    <dc:creator>RenuLalwani</dc:creator>
    <dc:date>2022-06-23T08:09:37Z</dc:date>
    <item>
      <title>Qlik Google BigQuery Connector: How to setup load from Large Datasets</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Google-BigQuery-Connector-How-to-setup-load-from-Large/ta-p/1937223</link>
      <description>&lt;P&gt;Google BigQuery limits cached results to approximately 10 GB compressed. Queries that return larger results overtake this limit and frequently result in the following error:&amp;nbsp;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;Response too large to return. Consider setting allowLargeResults to true in your job configuration&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H4&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Environment:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H4&gt;&lt;UL&gt;&lt;LI&gt;Qlik Google BigQuery Connector (Qlik Cloud)&lt;/LI&gt;&lt;LI&gt;Qlik Google BigQuery Connector (Qlik Sense Enterprise on Windows August 2021 and later)&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;&amp;nbsp;&lt;/H3&gt;&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Resolution&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H3&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To mitigate the "Response too large" error, you will have to set the queries to run with the Destination dataset specified&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;In Standard SQL, specify a destination table for the query results.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;In Legacy SQL, specify a destination table and set the allowLargeResults option.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Step by Step guide:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Create a destination dataset under your GBQ project&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image2022-5-30_15-45-24.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/80621iF19797EB3EC43965/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image2022-5-30_15-45-24.png" alt="image2022-5-30_15-45-24.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Make sure to set "Table expiration settings" for this dataset, as the temporary tables created by the driver will inherit the settings from the parent dataset.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image2022-5-30_15-46-57.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/80622i0205D1DF99D2594E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image2022-5-30_15-46-57.png" alt="image2022-5-30_15-46-57.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/LI&gt;&lt;LI&gt;Configure Qlik Google big query connector with the below settings&lt;BR /&gt;&amp;nbsp;&lt;BR /&gt;&lt;OL&gt;&lt;LI&gt;For Standard SQL, just provide the dataset name as shown below&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image2022-5-30_16-4-23.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/80624iF95BF9AFE036A1AF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image2022-5-30_16-4-23.png" alt="image2022-5-30_16-4-23.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;For Legacy SQL,&amp;nbsp; Select Legacy SQL from language Dilect, then enable Allow Large Result Sets checkbox and provide the dataset name as shown below&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image2022-5-30_16-8-41.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/80625i73408BEB44A1AF7A/image-size/medium?v=v2&amp;amp;px=400" role="button" title="image2022-5-30_16-8-41.png" alt="image2022-5-30_16-8-41.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;&lt;FONT size="3"&gt;Performance considerations:&lt;/FONT&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;As rightly quoted&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://cloud.google.com/bigquery/docs/best-practices-performance-output" target="_blank" rel="nofollow noopener"&gt;here&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;"&lt;SPAN&gt;Be aware that writing very large result sets to destination tables impacts query performance (I/O)", enabling large datasets settings will impact query performance and might slow down reloads.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So, to improve performance while working with destination tables strategy, its advisable to enable high throughput API&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image2022-5-30_16-54-15.png" style="width: 275px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/80626i69C05935E82D5B77/image-size/large?v=v2&amp;amp;px=999" role="button" title="image2022-5-30_16-54-15.png" alt="image2022-5-30_16-54-15.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Performance can be further be increased by using the alternate processing method for optimization reload by enabling Bulk Reader checkbox&amp;nbsp; (as shown in the screenshot above)&lt;/P&gt;&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;&lt;H4&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Related Content:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/H4&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Google BigQuery Docs: Writing large data results&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;A href="https://cloud.google.com/bigquery/docs/writing-results#large-results" target="_blank" rel="nofollow noopener"&gt;https://cloud.google.com/bigquery/docs/writing-results#large-results&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Google BigQuery Docs:&amp;nbsp;Manage query outputs &lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="https://cloud.google.com/bigquery/docs/best-practices-performance-output" target="_blank" rel="nofollow noopener"&gt;https://cloud.google.com/bigquery/docs/best-practices-performance-output&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;Qlik Cloud Help: Google BigQuery Connector load optimization settings&lt;BR /&gt;&lt;A href="https://help.qlik.com/en-US/connectors/Subsystems/ODBC_connector_help/Content/Connectors_ODBC/GoogleBigQuery/Create-GBQ-Connection.htm#anchor-8" target="_blank" rel="noopener"&gt;https://help.qlik.com/en-US/connectors/Subsystems/ODBC_connector_help/Content/Connectors_ODBC/GoogleBigQuery/Create-GBQ-Connection.htm#anchor-8&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2022 08:09:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Google-BigQuery-Connector-How-to-setup-load-from-Large/ta-p/1937223</guid>
      <dc:creator>RenuLalwani</dc:creator>
      <dc:date>2022-06-23T08:09:37Z</dc:date>
    </item>
  </channel>
</rss>

