Introduction to BigQuery jobs

This page provides an overview of BigQuery jobs.

BigQuery jobs

Jobs are actions that BigQuery runs on your behalf to load data, export data, query data, or copy data.

When you use the GCP Console, the classic BigQuery web UI, or the CLI to load, export, query, or copy data, a job resource is automatically created, scheduled, and run. You can also programmatically create a load, export, query, or copy job. When you create a job programmatically, BigQuery schedules and runs the job for you.

Because jobs can potentially take a long time to complete, they execute asynchronously and can be polled for their status. Shorter actions, such as listing resources or getting metadata are not managed by a job resource.

Required permissions

At a minimum, to run a job, you must have bigquery.jobs.create permissions. bigquery.jobs.create permissions are required for jobs that are automatically created by BigQuery, and they are required for jobs that you run programmatically.

The following predefined Cloud IAM roles include bigquery.jobs.create permissions:

• bigquery.user
• bigquery.jobUser
• bigquery.admin

For more information on Cloud IAM roles and permissions in BigQuery, see Access control.

Quota policy

For information about job quotas, see the documentation for the job type on the Quotas and limits page:

• Load jobs
• Copy jobs
• Export (extract) jobs
• Query jobs

Pricing

Every job is associated with a specific project that you specify. The billing account attached to the associated project is billed for any usage incurred by the job. If you share access to a project, any jobs run in the project are billed to the attached billing account.

For more information, see the Pricing page.

Next steps

• Learn how to run jobs programmatically.
• Learn how to manage jobs.