This section provides a complete list of the BigQuery properties you can configure in the connection string for this provider.

Whether or not to allow large datasets to be stored in temporary tables for large datasets.

bool

true

Whether or not to allow large datasets to be stored in temporary tables for large datasets.

This property determines where query results are stored in Google BigQuery.

 

string

""

Google BigQuery queries have a maximum amount of data they are allowed to return directly. If this limit is exceeded, then queries will fail with an error message like Response too large to return. When this option is enabled the response limit does not apply, because all query responses are stored in a Google BigQuery table before being returned.

This option is set differently depending upon whether your connection is using UseLegacySQL or not. By default this option is set using the standard SQL syntax:

When UseLegacySQL is enabled, this option is set using the legacy table syntax:

When using this option with multiple connections, make sure that each connection has its own destination table. Sharing a table between connections can lead to results getting lost because parallel queries can overwrite each others results.

Specifies whether to use Google BigQuery's built-in query cache.

bool

true

Google BigQuery will cache the results of recent queries, and will use this cache for queries by default. Google BigQuery automatically updates the cache when a table is modified, so performance is generally better without any risk of queries returning stale data.

If this is set to false, the query is always run against the table directly.

The number of results to return per page from Google BigQuery.

string

"100000"

The pagesize can control the number of results returned per page from Google BigQuery. Setting a higher pagesize will cause more data to come back in a single HTTP request, but may take longer to execute. Setting a smaller pagesize will increase the number of HTTP requests to get all the data, but is generally recommended to ensure timeout exceptions do not occur.

Note that this option does not have an effect if UseStorageApi is enabled and the queries being executed can be executed on the Storage API. See StoragePageSize for more information.

This determines how long to wait in seconds, between checks to see if a job has completed.

string

"1"

This only applies to queries which are stored to a table instead of streamed directly to the adapter. This applies in only three cases:

This property determines how long to wait between checking whether or not the query's results are ready. Very large resultsets or complex queries may take longer to process, and a low polling interval may result in may unnecessary requests being made to check the query status.

Whether or not to allow update without primary keys.

bool

false

Whether or not to allow update without primary keys.

Please set `AllowUpdatesWithoutKey` to true before you could use this property.

string

""

Remember setting `AllowUpdatesWithoutKey` to true before you could use this property:

Set the property like this:

Specifies whether to use BigQuery's legacy SQL dialect for this query. By default, Standard SQL will be used.

bool

false

If set to true, the query will use BigQuery's Legacy SQL dialect to rebuild the query. If set to false, the query will use BigQuery's standard SQL: https://cloud.google.com/bigquery/sql-reference/.

When UseLegacySQL is set to false, the values of AllowLargeResultSets is ignored. The query will be run as if AllowLargeResultSets is true.