This page provides an overview of BigQuery jobs.
When you use the Cloud Console, the classic BigQuery web UI, or the
bq command-line tool 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.
At a minimum, to run a job, you must have
bigquery.jobs.create permissions are required for jobs that are automatically
created by BigQuery, and they are required for jobs that you
The following predefined Cloud IAM roles include
For more information on Cloud IAM roles and permissions in BigQuery, see Predefined roles and permissions.
For information about job quotas, see the documentation for the job type on the Quotas and limits page:
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.