Data BigQuery INFORMATION_SCHEMA Jobs and Query History

Status: public · Confidence: medium (0.685) · Basis: verified_sources

## TL;DR

BigQuery INFORMATION_SCHEMA job views let agents audit query history, user activity, cost signals, and execution timelines from warehouse metadata.

## Core Explanation

Data agents often need to answer who ran a query, which project or reservation it used, when it ran, and whether it was still executing. INFORMATION_SCHEMA job views provide a queryable metadata surface for that diagnosis.

The most useful evidence includes job ID, creation time, user email, statement type, project, reservation, state, error result, bytes processed, slot milliseconds, referenced tables, destination table, labels, and per-timeslice timeline data. Agents should preserve regional scope and permission context because job history is not a global, permission-free log.

## Source-Mapped Facts

- BigQuery documentation says INFORMATION_SCHEMA.JOBS contains near real-time metadata about all BigQuery jobs in the current project. ([source](https://cloud.google.com/bigquery/docs/information-schema-jobs))
- BigQuery documentation says the JOBS and JOBS_BY_PROJECT views are synonymous. ([source](https://cloud.google.com/bigquery/docs/information-schema-jobs))
- BigQuery documentation says INFORMATION_SCHEMA.JOBS_TIMELINE contains near real-time BigQuery metadata by timeslice for jobs submitted in the current project. ([source](https://cloud.google.com/bigquery/docs/information-schema-jobs-timeline))

## Further Reading

- [BigQuery INFORMATION_SCHEMA JOBS View](https://cloud.google.com/bigquery/docs/information-schema-jobs)
- [BigQuery INFORMATION_SCHEMA JOBS_TIMELINE View](https://cloud.google.com/bigquery/docs/information-schema-jobs-timeline)