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.
| Field | Required | Default | Notes |
|---|---|---|---|
| Host | Yes | bigquery.googleapis.com | HTTPS endpoint; the connection is always encrypted. |
| Credential | Yes | — | A service-account key (JSON) or token; stored in the OS keyring. |
| Project ID | Yes | — | Your Google Cloud project. |
| Dataset | No | — | The dataset to browse. |
| Location | No | — | The dataset region (for example US or EU). |
Connect with the form
- 1Choose BigQuery
Open the launcher and pick the BigQuery card.
- 2Add the service account
Paste or select the service-account key (JSON); it is saved to the OS keyring.
- 3Enter the project ID
Use the Google Cloud project that owns the data.
- 4Choose a dataset and location (optional)
Set the dataset to browse and its region.
- 5Save 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
| Symptom | Likely cause | Fix |
|---|---|---|
| Invalid credentials / permission denied | The service account lacks access, or the key is wrong. | Grant BigQuery roles to the service account and re-check the key. |
| Project not found | Wrong project ID. | Re-check the project ID in the Google Cloud console. |
| Dataset not found | The dataset does not exist in the project or location. | Re-check the dataset name and its location. |
| Not found: location | Wrong dataset region. | Set the Location to match the dataset's region. |