Exploring the BigQuery Query History

Senior Data Engineer • Contractor / Freelancer • GCP & AWS Certified
Search for a command to run...

Senior Data Engineer • Contractor / Freelancer • GCP & AWS Certified
No comments yet. Be the first to comment.
Hands-on guides to data tooling, infrastructure, and operations — scheduling, pipelines, access control, and the engineering behind data workflows.
In a previous post, I mentioned Remote Functions—a powerful way to send data from BigQuery to an external service for processing, including a Cloud Run function. This is especially useful when SQL lacks built-in support for your specific needs, and w...
Here's a useful Dataform concept: pre_operations and post_operations. As the name implies, these represent a set of actions that run before and after the main operation (table, view, or SQL operations

BigQuery has always been a SQL engine for tabular data. Object tables add an interesting twist to that. Instead of rows containing values, an object table gives you one row per file — pointing at da

Query your data lake with warehouse-grade security and performance — without moving a single file.

Ever run a heavy BigQuery SQL query, processed gigabytes of data — and then accidentally closed the tab or forgot to save the results? 😬 Don't re-run it. Your results are still there. BigQuery automa

You can use query parameters in BigQuery hashtag#SQL (now in the console as well!) — but how are they different from variables, and when should you use each? Both parameters and variables act as place

title: "Exploring the BigQuery Query History" seoTitle: "Understanding BigQuery Query History" seoDescription: "Discover how BigQuery's Job History helps track and retrieve past queries efficiently with filtering options and saved results for recent queries" datePublished: Wed Feb 19 2025 09:46:00 GMT+0000 (Coordinated Universal Time) cuid: cm7bqa747000o09l54f2jex14 slug: exploring-the-bigquery-query-history cover: https://cdn.hashnode.com/res/hashnode/image/stock/unsplash/afW1hht0NSs/upload/7044ae79c50580b2b3314f80f33f5bff.jpeg tags: databases, google-cloud, sql, bigquery, gcp, data-engineering
Here’s a BigQuery trick I use all the time—seriously, not saying this to make my post catchier 😁.
It’s not flashy or very complicated, but it’s one of my favorites: Job History.
Under the Query Editor, you’ll find Job History, which stores all past queries—either your own (Personal History) or those run by others in the project (Project History).
🔍 Why is this useful?
✅ Quickly find queries you forgot to save.
✅ Filter by date, SQL definition (summary), or user to track down past work.
✅ For recent queries, you might even retrieve results from the temporary table—saving you from rerunning expensive queries.
This has saved me so many times after accidentally closing a query tab. (Just remember: if you never executed the query, it won’t be there!)
Also, please be reminded that the job data is also available via an INFORMATION SCHEMA view (check out the comments for a post about that one).
Found it useful? Subscribe to my Analytics newsletter at notjustsql.com.
Enjoyed this? Here are some related articles you might find useful: