Data location checkpoint
Before you write SQL, confirm that you can name the exact table.
Your Organizer Query Brief needs the full path:
project.dataset.table
This path matters because many projects can contain many datasets, and many datasets can contain many tables. A plain table name like signups may not be specific enough. BigQuery needs to know where the table lives.
You should also know whether you are using a training project, a public dataset, or a team-owned dataset.
BigQuery can be used through a free Google Cloud project. New users may see information about cloud credits or billing setup. For this course, learners can use the sandbox or a provided training environment, so they do not need to add a credit card for the learning activities.
Checkpoint
Fill this in:
For my Organizer Query Brief, I will inspect this table: [project].[dataset].[table]
Then answer:
- What project contains the table?
- What dataset contains the table?
- What is the table name?
- Why does this table seem relevant to your organizing question?
Add the Data location section to your Organizer Query Brief.
Brief section template
I plan to look at the table [project.dataset.table] because [reason it might help]. I am still unsure about [caveat : data freshness, geography, sample size].
Worked example
I plan to look at the table `bigquery-public-data.usa_names.usa_1910_current` because it has baby name counts by state and year and I can use it to practice filtering Georgia and grouping by year. I am still unsure about how recent the data goes and whether name counts under 5 are suppressed for privacy.
Which container?
In BigQuery, which container holds datasets and is also where access and billing are managed?
You earned the Console Navigator badge
You can move around BigQuery and you have a real table picked. In Module 3 you will inspect that table's schema, preview rows, and check the row count before writing a single query.
Next: Module 3 · Reading a Table: Schema, Preview, Row Counts
Continue to Module 3