On the BigQuery Data Source setup screen, the Project ID and JSON Key File are always required. You can get a key file when you create a new service account with Google (details below).
- If your database schema exceeds 5000 tokens, untick the Load Schema box to stop Redash from loading it to the Query Editor screen. Many browsers will slow down or crash if the schema is too big.
- Since BigQuery 2.0, BigQuery supports its Legacy SQL syntax or Standard SQL Syntax. Redash supports both, but Standard SQL is the default. This preference applies at the Data Source level by toggling the Use Standard SQL box. Your selection here is passed to BigQuery along with your query text. If some of your queries use Legacy SQL and others use Standard SQL, you can create two Data Sources.
- You can read more about Processing Location here. If you receive a job not found an error that looks like this:
Not found: Job <project_id>:<job_id>, check that your Processing Location is correct.
- If you enter a Scanned Data Limit, Redash will perform a dry-run when you execute your query to check how much data will be processed. And if it is larger than the limit you specify, an error will appear.
- The Maximum Billing Tier is an integer number that Redash can pass along to BigQuery via their API. See their documentation for more info.
How to create a Google Service Account?
- Open the API Credentials Page. If prompted, select or create a project.
- Click the “Create credentials” button. On the dropdown that appears, chose “Service account key”.
- On the following page, use the dropdown to select the project you elected in step 1. For role select
BigQuery Adminfrom the tree menu.
- Under key type, select JSON and hit “Create”
.json file will then download to your computer. Use this when setting up your Data Source.
If you’re using the predefined roles in BigQuery, you need to use the admin role since it’s the only one that can create queries and list tables.
Want to create your own role? The permissions you need to assign are: