You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can better measure our usage of bigquery by making queries like this:
SELECT*FROM`region-us`.INFORMATION_SCHEMA.JOBS_BY_PROJECT--`region-us` gets results for all jobs in the US region
This query allows us to track usage data for each of our queries. The schema is defined here. We should be able to determine the total bytes processed as actually see the most costly queries here. Additionally, each of the jobs listed has the user that executed the job as well as a plethora of other potentially useful information to understand the operation of each query.
To determine costs, we would simply need to multiply "bytes processed" by bigquery's pricing model.
The text was updated successfully, but these errors were encountered:
What is it?
We can better measure our usage of bigquery by making queries like this:
This query allows us to track usage data for each of our queries. The schema is defined here. We should be able to determine the total bytes processed as actually see the most costly queries here. Additionally, each of the jobs listed has the user that executed the job as well as a plethora of other potentially useful information to understand the operation of each query.
To determine costs, we would simply need to multiply "bytes processed" by bigquery's pricing model.
The text was updated successfully, but these errors were encountered: