Intro to SQLfor Organizing
Module 2 · BigQuery Setup and Interface 2.4 Locate a real table
Subsection 2.4

Locate a real table

~5 min

Reading

To answer a data question, you need to locate the table that holds the relevant records.

A table is a structured set of rows and columns. Each column has a name and a data type. Each row contains one record. The schema defines the structure of the table: what fields exist, what type of data they hold, and sometimes whether values can be missing.

When you browse in BigQuery, you may see several icons:

  • Project icon: a top-level Google Cloud container.
  • Dataset icon: a collection or stack of related objects.
  • Table icon: a grid or spreadsheet-style object that stores data.
  • View icon: a virtual table defined by a saved SQL query.
  • Materialized view icon: a view-like object that stores precomputed results for speed.
  • Add icon: creates a new resource.
  • Refresh icon: updates the list of resources or results.
  • Trash icon: deletes a resource; use this carefully.
  • Query history or job history icon: shows past queries and jobs.
  • Gear icon: settings or configuration.

For this course, your goal is not to understand every icon. Your goal is to find one table you can inspect and eventually query.

Use the Explorer panel to move from project to dataset to table. When you click a table, BigQuery opens information about that table in a tab. You can inspect schema, details, preview, and sometimes lineage.

A full table path uses this pattern:

project.dataset.table

In BigQuery SQL, you often wrap the full path in backticks:

`project.dataset.table`

Learner action

Choose one table for your brief. Copy its full project.dataset.table path.

Time to connect the interface to your Module 1 question. By the end of this page you will have written down one real project.dataset.table path that you plan to inspect.

Suggested starter datasets

  • bigquery-public-data.usa_names.usa_1910_current : baby name counts by state and year. Great for filtering, grouping, and sorting practice.
  • bigquery-public-data.census_bureau_acs.county_2020_5yr : county-level demographic estimates from the American Community Survey.
  • bigquery-public-data.google_political_ads.creative_stats : Google political ad spending and impressions.
  • bigquery-public-data.openaq.global_air_quality : global air quality readings.

If your team has its own project shared with you, that works too. Pick whichever feels closest to the question you wrote in Module 1.

Activity steps

  1. Re-read the organizing question you wrote in Module 1.
  2. Decide whether you are using a public dataset (recommended) or a team dataset.
  3. Open the project in the Explorer panel and expand it.
  4. Open a dataset that could plausibly answer your question.
  5. Click one specific table inside it. Look at its schema briefly to confirm it could matter.
  6. Write down the full path: project.dataset.table.

Watch for two common pitfalls

Wrong separator: BigQuery uses dots between project, dataset, and table, never slashes. Dataset vs table: A dataset is a folder. Make sure you have drilled all the way down to a single table before you copy the path.

Once you know which dataset and table you're in, you can ask questions of the other tables too. We have an events table alongside voter_file : try counting events in a specific county.

Action: Write your project.dataset.table path into your running brief.