How Ridge works with BigQuery
What you can do
- Connect to a BigQuery project and read its tables
- Reference a table directly, or shape it with a custom SQL query
- Filter and aggregate at the source with
WHEREandGROUP BY - Refresh on a schedule with standard cron expressions
What you'll need
Two pieces of information connect Ridge to your project. Collect these from Google Cloud before you start.
Set up the connection
1 Create a Connection
On the Data page, click New Connection and choose BigQuery as the type. Enter the credentials you gathered, then save.
- Project — your GCP project id
- Service Account JSON — the service-account key JSON
2 Create a Dataset
Back on the Data page, click New, select source Connection, and pick the BigQuery connection you just created. A Data Set points at a specific table and can carry its own query and refresh schedule.
3 Select a table, or write a query
Choose how Ridge reads from the project. A direct table reference is simplest; custom SQL lets you filter and aggregate at the source.
4 Schedule ingestion
Set an ingestion schedule with standard cron syntax, then save. Ridge runs your query against BigQuery and stores the results, ready for analysis.
Best practices
A few habits keep ingestion fast, secure, and predictable.
Supported features & limitations
Troubleshooting
Most connection issues fall into four buckets. Expand the one that matches your error.
Invalid credentials
"invalid serviceaccountcredentials", "could not parse PEM", "invalid_grant", 401, "unauthorized"
Your service-account key is bad or expired. Re-download the JSON key from Google Cloud and re-enter it.
Insufficient permissions
403, "permission denied", "does not have bigquery.…", "Permission bigquery.tables.get denied"
The service account lacks rights. Grant it BigQuery Data Viewer on the dataset (and Job User on the project).
Resource not found
404, "not found", "does not exist", DuckDB "Invalid table string"
The project, dataset, or table is wrong. Fix the project.dataset.table identifier.
Network unreachable
"could not resolve host", "timed out", "connection refused"
The endpoint is unreachable. Check your egress allowlist.
.avif)