Computer Science · Grade 10

Active learning ideas

Querying Data with SQL Basics

Active learning works for SQL basics because students need to write and test queries themselves to understand how data retrieval actually functions. Hands-on practice removes the abstract nature of database concepts, making it clear how commands like SELECT or WHERE behave in real time. Relational databases come alive when students interact with them, rather than just reading about them.

• Ontario Curriculum Expectations
• CS.HS.D.4
• CS.HS.D.5

• 20–40 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Stations Rotation
• 35 min · Small Groups

Query Challenge Relay: Basic SELECT Stations

Divide class into teams at computers with a shared database of fictional sales records. Each team member writes one query segment (SELECT, WHERE, ORDER BY) then tags the next teammate. First team to run a complete query and explain results wins. Debrief as whole class.

Construct basic SQL queries to extract specific information from a database.

Facilitation Tip

During Query Challenge Relay, set a timer for each station so students focus on writing correct queries quickly, then rotate to see peer solutions.

What to look for

Provide students with a small, pre-defined database table (e.g., a list of students with names, grades, and subjects). Ask them to write a single SQL query to find all students who scored above 80% in Math. Review their queries for correct syntax and logic.

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

Activity 02

• Stations Rotation
• 25 min · Pairs

Pairs Debug: Fix the Query

Provide pairs with 5 broken SQL queries on a student enrollment database. They identify errors like missing commas or wrong operators, rewrite, and test. Pairs then swap with another duo for peer review and retesting.

Analyze the results of different filtering and sorting operations.

Facilitation Tip

When pairs debug queries, provide printed error messages with red pen marks so students practice identifying syntax issues visually.

What to look for

On an index card, have students write an SQL query that retrieves the names and ages of all employees hired after a specific date (provide the date). Then, ask them to write one sentence explaining how their query filters the data.

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

Activity 03

• Stations Rotation
• 40 min · Whole Class

Scenario Solve: Whole Class Query Build

Present a decision-making scenario, such as selecting event volunteers from a database. Project the database schema. Class votes on query clauses step-by-step, tests iteratively, and discusses result impacts.

Explain how database queries support decision-making processes.

Facilitation Tip

For Scenario Solve, display the database schema on the board so every student can reference it while building queries together.

What to look for

Present a scenario, such as a school wanting to identify students who participate in at least two extracurricular activities. Ask students: 'What SQL clauses would you need to use to find this information, and why?' Facilitate a brief class discussion on their approaches.

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

Activity 04

• Stations Rotation
• 20 min · Individual

Individual Exploration: Custom Queries

Give students a music library database. They write 3 personal queries, like top artists by play count with filters. Share one via class forum for feedback.

Construct basic SQL queries to extract specific information from a database.

What to look for

Provide students with a small, pre-defined database table (e.g., a list of students with names, grades, and subjects). Ask them to write a single SQL query to find all students who scored above 80% in Math. Review their queries for correct syntax and logic.

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

A few notes on teaching this unit

Teach SQL basics by starting with small, real databases students can see and touch, like class rosters or library inventories. Model the habit of reading schema first and typing queries slowly, since rushing leads to missing table relationships. Avoid jumping straight to complex joins; build comfort with single-table queries first. Research shows students grasp SQL better when they connect commands to actions they perform in everyday life, like sorting a playlist or filtering a shopping list.

Successful learning looks like students confidently writing correct SQL queries that retrieve, filter, and sort data from multiple tables. They should explain their query logic, troubleshoot errors, and connect SQL commands to real-world data needs. Group discussions should show students discussing filtering logic and output structure without relying on guesswork.

---

Watch Out for These Misconceptions

• During Query Challenge Relay, watch for students who hesitate to run queries because they believe SELECT changes the database.

  Have students run SELECT queries in the relay and then immediately show the unchanged table, reinforcing that retrieval does not alter data. Ask them to contrast this with UPDATE commands they might see later.

• During Pairs Debug: Fix the Query, watch for students who treat WHERE clauses like programming if-statements.

  Ask pairs to test WHERE conditions one at a time and observe how rows disappear from output. Use the debug sheet to circle each condition and label it as a filter, not a branch.

• During Scenario Solve: Whole Class Query Build, watch for students who describe databases as spreadsheets without relationships.

  Have the class build a query that joins two tables, then sketch the relationships on the board. Point to the join condition and ask students to describe how the tables connect through keys.

---

Methods used in this brief

• Stations Rotation