BigQuery for analytics in GCP - Commands & Configuration

Introduction

BigQuery helps you analyze large amounts of data quickly without needing to manage servers. It solves the problem of slow data analysis by using Google's powerful cloud infrastructure.

When you want to analyze sales data from your online store to find trends.

When you need to process large logs from your website to understand user behavior.

When you want to combine data from different sources to create reports.

When you need to run complex queries on big datasets without setting up a database.

When you want to share data insights with your team using a simple SQL interface.

Commands

This command creates a new dataset named 'dataset_example' in BigQuery to organize your tables.

Terminal

bq mk dataset_example

Expected Output

Dataset 'project_id:dataset_example' successfully created.

This command loads data from a CSV file in Google Cloud Storage into the 'sales_data' table in your dataset, using the schema defined in 'schema.json'.

Terminal

bq load --source_format=CSV dataset_example.sales_data gs://my-bucket/sales_data.csv schema.json

Expected Output

Waiting on bqjob_r1234567890_000001...

Job succeeded.

→

--source_format - Specifies the format of the source data file.

This command runs a SQL query to find the top 5 products by total quantity sold in the 'sales_data' table.

Terminal

bq query --use_legacy_sql=false 'SELECT product, SUM(quantity) as total_quantity FROM dataset_example.sales_data GROUP BY product ORDER BY total_quantity DESC LIMIT 5;'

Expected Output

product    total_quantity

ProductA  150

ProductB  120

ProductC  100

ProductD  80

ProductE  60

→

--use_legacy_sql=false - Ensures the query uses standard SQL syntax.

This command shows the details of the 'sales_data' table, including schema and metadata.

Terminal

bq show dataset_example.sales_data

Expected Output

Table project_id:dataset_example.sales_data

   Last modified          Schema

   2024-06-01 12:00:00    product:STRING, quantity:INTEGER, price:FLOAT

Key Concept

If you remember nothing else from this pattern, remember: BigQuery lets you run fast SQL queries on big data without managing servers.

Common Mistakes

Using legacy SQL syntax without setting the flag

The default BigQuery SQL mode may not support modern SQL features, causing query errors.

Always use --use_legacy_sql=false to run standard SQL queries.

Not specifying the correct source format when loading data

BigQuery may fail to load the data or interpret it incorrectly.

Use --source_format flag to specify the correct format like CSV or JSON.

Trying to query a table before loading data into it

The query will fail because the table does not exist or is empty.

Create the dataset and load data before running queries.

Summary

Create a dataset to organize your data tables.

Load data from cloud storage into BigQuery tables with the correct format and schema.

Run SQL queries using standard SQL to analyze your data quickly.

Check table details to understand your data structure.

Practice

1. What is the main purpose of Google BigQuery in data analytics?

easy

A. To run fast SQL queries on large datasets without managing servers

B. To store files like images and videos

C. To create virtual machines for computing

D. To send emails automatically

Solution

1. Step 1: Understand BigQuery's role

   BigQuery is designed to analyze large amounts of data quickly using SQL without needing to manage servers.

2. Step 2: Compare options

   Options A, C, and D describe other services unrelated to BigQuery's main function.

3. Final Answer:

   To run fast SQL queries on large datasets without managing servers -> Option A

4. Quick Check:

   BigQuery = fast SQL analytics [OK]

Hint: BigQuery = fast SQL on big data, no servers needed [OK]

Common Mistakes:

• Confusing BigQuery with storage or compute services
• Thinking BigQuery manages virtual machines
• Assuming BigQuery sends emails

2. Which of the following is the correct syntax to select all columns from a table named sales_data in BigQuery?

easy

A. FETCH * sales_data;

B. GET ALL FROM sales_data;

C. SELECT * FROM sales_data;

D. SELECT ALL COLUMNS sales_data;

Solution

1. Step 1: Recall SQL SELECT syntax

   The correct SQL syntax to select all columns is SELECT * FROM table_name;.

2. Step 2: Check each option

   Only SELECT * FROM sales_data; matches the correct SQL syntax. Options A, B, and D use incorrect keywords or structure.

3. Final Answer:

   SELECT * FROM sales_data; -> Option C

4. Quick Check:

   SELECT * FROM table = correct syntax [OK]

Hint: Use SELECT * FROM table to get all columns [OK]

Common Mistakes:

• Using wrong keywords like GET or FETCH
• Omitting FROM keyword
• Writing SELECT ALL COLUMNS instead of SELECT *

3. Given the table orders with columns order_id, customer_id, and amount, what will this query return?

SELECT customer_id, SUM(amount) AS total_spent FROM orders GROUP BY customer_id ORDER BY total_spent DESC LIMIT 2;

medium

A. All orders sorted by amount

B. Top 2 customers who spent the most money

C. Total amount spent by all customers combined

D. First 2 orders by order_id

Solution

1. Step 1: Understand the query components

   The query groups orders by customer_id, sums the amount per customer, orders results by total spent descending, and limits output to 2 rows.

2. Step 2: Interpret the output

   This returns the top 2 customers who spent the most money.

3. Final Answer:

   Top 2 customers who spent the most money -> Option B

4. Quick Check:

   GROUP BY customer_id + SUM + ORDER BY DESC + LIMIT 2 = top 2 spenders [OK]

Hint: GROUP BY + SUM + ORDER BY DESC + LIMIT = top results [OK]

Common Mistakes:

• Thinking it returns all orders instead of grouped data
• Confusing LIMIT with total sum
• Ignoring ORDER BY direction

4. You wrote this query but get an error:

SELECT customer_id, amount FROM orders WHERE SUM(amount) > 100;

What is the problem?

medium

A. SELECT must include all columns in WHERE

B. Missing GROUP BY clause for customer_id

C. amount column does not exist

D. SUM() cannot be used in WHERE clause; use HAVING instead

Solution

1. Step 1: Identify misuse of SUM() in WHERE

   Aggregate functions like SUM() cannot be used in WHERE; they belong in HAVING clause.

2. Step 2: Correct usage

   Replace WHERE SUM(amount) > 100 with HAVING SUM(amount) > 100 and add GROUP BY customer_id.

3. Final Answer:

   SUM() cannot be used in WHERE clause; use HAVING instead -> Option D

4. Quick Check:

   Aggregates in HAVING, not WHERE [OK]

Hint: Use HAVING for conditions on aggregates, not WHERE [OK]

Common Mistakes:

• Using SUM() in WHERE clause
• Forgetting GROUP BY with aggregates
• Assuming WHERE filters aggregates

5. You want to find the average order amount per customer but only for customers who placed more than 5 orders. Which query correctly achieves this in BigQuery?

hard

A. SELECT customer_id, AVG(amount) AS avg_amount FROM orders GROUP BY customer_id HAVING COUNT(order_id) > 5;

B. SELECT customer_id, AVG(amount) AS avg_amount FROM orders WHERE COUNT(order_id) > 5 GROUP BY customer_id;

C. SELECT customer_id, AVG(amount) AS avg_amount FROM orders WHERE order_count > 5;

D. SELECT customer_id, AVG(amount) AS avg_amount FROM orders GROUP BY customer_id WHERE COUNT(order_id) > 5;

Solution

1. Step 1: Understand filtering on aggregate

   To filter groups by count, use HAVING clause after GROUP BY.

2. Step 2: Check each option's correctness

   SELECT customer_id, AVG(amount) AS avg_amount FROM orders GROUP BY customer_id HAVING COUNT(order_id) > 5; uses GROUP BY customer_id and HAVING COUNT(order_id) > 5 correctly. Options A, B, and C misuse WHERE or clause order.

3. Final Answer:

   SELECT customer_id, AVG(amount) AS avg_amount FROM orders GROUP BY customer_id HAVING COUNT(order_id) > 5; -> Option A

4. Quick Check:

   HAVING filters groups, WHERE filters rows [OK]

Hint: Use HAVING to filter groups after GROUP BY [OK]

Common Mistakes:

• Using WHERE to filter aggregates
• Placing WHERE after GROUP BY
• Referencing undefined columns like order_count