Documentation

BigQuery

Connect TableR to Google BigQuery with a service account, project and dataset fields, verifying the connection, and troubleshooting.

BigQuery is Google Cloud's serverless data warehouse. TableR connects over HTTPS and authenticates with a service account; provide your project and dataset to start querying.

Overview

TableR talks to BigQuery through the Google Cloud APIs over HTTPS. There is no host or port to manage — you authenticate with a service-account key and point TableR at a project and dataset.

  • Serverless — no server, host, or port to run; reached at bigquery.googleapis.com over HTTPS.
  • Authentication — a Google Cloud service-account key (JSON) or token.
  • Scope — a project holds datasets, and a dataset holds tables.

Before you start

  • A Google Cloud project ID.
  • A service-account key (JSON) or token with BigQuery access.
  • The dataset you want to browse.
  • The dataset location (region), if it is not the default.

Connection fields

These fields match TableR's BigQuery connection form. The service-account key is stored in the operating system keyring, never in plain configuration files.

FieldRequiredDefaultNotes
HostYesbigquery.googleapis.comHTTPS endpoint; the connection is always encrypted.
CredentialYesA service-account key (JSON) or token; stored in the OS keyring.
Project IDYesYour Google Cloud project.
DatasetNoThe dataset to browse.
LocationNoThe dataset region (for example US or EU).

Connect with the form

  1. 1
    Choose BigQuery

    Open the launcher and pick the BigQuery card.

  2. 2
    Add the service account

    Paste or select the service-account key (JSON); it is saved to the OS keyring.

  3. 3
    Enter the project ID

    Use the Google Cloud project that owns the data.

  4. 4
    Choose a dataset and location (optional)

    Set the dataset to browse and its region.

  5. 5
    Save and connect

    Save the profile so it reappears in the launcher, then connect.

Verify the connection

Once connected, open a SQL tab and run a quick check:

SELECT CURRENT_TIMESTAMP();
SELECT SESSION_USER();

If both statements return rows, the connection and credentials are working.

Troubleshooting

SymptomLikely causeFix
Invalid credentials / permission deniedThe service account lacks access, or the key is wrong.Grant BigQuery roles to the service account and re-check the key.
Project not foundWrong project ID.Re-check the project ID in the Google Cloud console.
Dataset not foundThe dataset does not exist in the project or location.Re-check the dataset name and its location.
Not found: locationWrong dataset region.Set the Location to match the dataset's region.

Next steps