Export query results to Blob Storage

This document describes how to export the result of a query that runs against a BigLake table to your Azure Blob Storage.

For information about how data flows between BigQuery and Azure Blob Storage, see Data flow when exporting data.

Before you begin

Ensure that you have the following resources:

Export query results

BigQuery Omni writes to the specified Blob Storage location regardless of any existing content. The export query can overwrite existing data or mix the query result with existing data. We recommend that you export the query result to an empty Blob Storage container.

  1. In the Google Cloud console, go to the BigQuery page.

    Go to BigQuery

  2. In the Query editor field, enter a GoogleSQL export query:


    Replace the following:

    • CONNECTION_REGION: the region where the connection was created.
    • CONNECTION_NAME: the connection name that you created with the necessary permission to write to the container.
    • AZURE_STORAGE_ACCOUNT_NAME: the name of the Blob Storage account to which you want to write the query result.
    • CONTAINER_NAME: the name of the container to which you want to write the query result.
    • FILE_PATH: the path where you want to write the exported file to. It must contain exactly one wildcard * anywhere in the leaf directory of the path string, for example, ../aa/*, ../aa/b*c, ../aa/*bc, and ../aa/bc*. BigQuery replaces * with 0000..N depending on the number of files exported. BigQuery determines the file count and sizes. If BigQuery decides to export two files, then * in the first file's filename is replaced by 000000000000, and * in the second file's filename is replaced by 000000000001.
    • FORMAT: supported formats are JSON, AVRO, CSV, and PARQUET.
    • QUERY: the query to analyze the data that is stored in a BigLake table.


If you get an error related to quota failure, then check if you have reserved capacity for your queries. For more information about slot reservations, see Before you begin in this document.


For a full list of limitations that apply to BigLake tables based on Amazon S3 and Blob Storage, see Limitations.

What's next