--- title: "Google BigQuery" slug: "google-bigquery-overview" updated: 2026-11-03T12:45:28Z published: 2026-11-03T12:45:28Z canonical: "skthelp.syniti.com/google-bigquery-overview" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # Google BigQuery ## Overview The Syniti Knowledge Platform (SKP) provides support for integrating with Google BigQuery using REST APIs. Replicate Preview allows you to use Google BigQuery as both a **source** and **target** in replication workspaces, limited to **Snapshot (Refresh)** replication mode. This article covers how to create BigQuery datastore connection and configure BigQuery datastores for replication at a high-level. ### Prerequisites Before creating a refresh replication for **source** or **target** using your BigQuery datasets and tables, ensure that you complete the following configurations: - **BigQuery Datastore and Connection:** A BigQuery datastore and connection needs to be created in the required system in the Catalog module. Refer to [Create a Connection](/v1/docs/create-a-connection) and [Connecting to Google BigQuery](/v1/docs/connecting-to-google-bigquery) for more information. > [!NOTE] > Note > > - When creating a datastore connection to BigQuery: > > These values are required to scope BigQuery operations to the specific project and dataset you want to access. Refer to [Creating and managing projects](https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects) and [BigQuery Datasets](https://docs.cloud.google.com/bigquery/docs/datasets-intro) for more information. > - **Database**: Enter your Google Cloud **Project ID**. > - **Schema**: Enter your BigQuery **Dataset** name. > - Select **Import All** to ingest metadata of all tables present in the BiqQuery dataset. - **User Permissions:** Users do not need individual BigQuery permissions. The Syniti OAuth2 client is pre-configured with all required BigQuery permissions. However, your Google developer account (user identity) is required for authentication (tracking and audit) only, not authorization. - If you are using this connection as a source, run a scan to ingest metadata from this connection's objects into the SKP. ## BigQuery as a Source In a Replicate Preview workspace, create a source datastore using the BigQuery datastore connection for the required target datastore. Refer to the [Creating Source Datastores](/v1/docs/configure-workspace-datastores#creating-source-datastores) section for more information. Create the required replications either by using the [Source Table Selection](/v1/docs/configure-workspace-datastores#selecting-source-tables) dialog box or by [adding them manually](/v1/docs/configure-workspace-datastores#adding-manual-replications). ### Source Considerations - **Snapshot Replication:** BigQuery supports full table scans for snapshot (refresh) replication, allowing you to replicate entire datasets or specific tables to your target datastore. - **Large Datasets:** BigQuery efficiently handles large datasets. The SKP automatically manages pagination to retrieve all records from your source tables. - **Query Performance:** BigQuery's query optimizer ensures efficient data retrieval. Monitor your usage to manage costs, as BigQuery charges per byte scanned. Refer to [BigQuery Quotas and Limits](https://cloud.google.com/bigquery/quotas) for more information. ## BigQuery as a Target In a Replicate Preview workspace, create a target datastore using the BigQuery datastore connection. Refer to the [Creating Target Datastores](/v1/docs/configure-workspace-datastores#creating-target-datastores) section for more information. > [!NOTE] > Note > > Configure your target replication settings by specifying write options (Truncate (default), Append, Drop) and defining [table mappings](/v1/docs/performing-field-mappings) from your source to BigQuery tables. ### Target Considerations - **Auto Table Creation:** The SKP supports automatic table creation in a BigQuery dataset. If a target table doesn't exist, it will be created based on the source table schema. - **Write Options:** - **Append:** Inserts new records into existing BigQuery tables without modifying existing data. - **Truncate:** Truncates existing data and reloads the table with data from the source. - **Drop Target Table:** Drops and recreates the target table and reloads the table with data from the source. - **Cost Optimization:** Monitor your BigQuery storage and query costs. Refer to [BigQuery Pricing](https://cloud.google.com/bigquery/pricing) for detailed cost information. ## Important Notes - **Metadata Discovery:** After adding tables to your BigQuery datastore, metadata is automatically scanned and imported. This process may take some time for large datasets. - **Dataset Permissions:** Ensure your service account has permissions to both read from source datasets and write to target datasets. - **Regional Considerations:** BigQuery datasets are region-specific. Ensure your source and target datasets are in regions that meet your compliance and performance requirements. - **Connection Testing:** Always test your BigQuery connections to verify authentication and permissions are correctly configured before running large-scale replications. ## Related Articles - [Adding Manual Replications](/v1/docs/configure-workspace-datastores#adding-manual-replications) - [Configure Workspace: Datastores](/v1/docs/configure-workspace-datastores) - [Connecting to Google BigQuery](/v1/docs/connecting-to-google-bigquery) - [Create a Connection](/v1/docs/create-a-connection) - [Datastores](/v1/docs/datastores) - [Performing Field Mappings](/v1/docs/performing-field-mappings)