Large Result Set Support
BigQuery imposes a maximum response size on all requests. If you do not enable large result set support, when executing queries, you might encounter an error message such as "Response too large to return".
If you expect your query to return a large result set, do the following to make sure that the query results can be returned as expected:
- If you are using standard SQL, specify a destination dataset and table for storing the query results. To do this, set the
LargeResultDatasetandLargeResultTableproperties, respectively. - If you are using legacy SQL, enable support for large result sets, and then specify a destination dataset and table for storing the query results. To do this, enable the
AllowLargeResultsproperty, and then set theLargeResultDatasetandLargeResultTableproperties to the destination dataset and table, respectively.
Important:
- When the
LargeResultDatasetandLargeResultTableproperties are set, all query results are written to and read from the those tables regardless of the query and its result size. Because of this, the result cache is not available for subsequent queries, and you are billed for every query that you make. - Working with large data sets may cause you to reach the query limits defined in Google BigQuery. For information about query limits, see "Quotas & Limits" in the Google BigQuery documentation: https://cloud.google.com/bigquery/quotas.
In both standard and legacy SQL, if you do not specify a destination dataset or table, the connector stores large result sets in a temporary, default location. The default dataset is hidden, and is named "_simba_jdbc". The default table has a name consisting of the prefix "temp_table" followed by the time of table creation and a randomized ID. These datasets and tables are deleted after 24 hours.