Technologies · Year 10

Active learning ideas

Relational Databases and SQL

Active learning builds relational schema thinking by letting students experience the friction of real data problems, where flat structures collapse under updates and queries break without proper keys. Hands-on activities make abstract concepts like normalization and JOINs visible through tangible outcomes, so students see why constraints exist rather than memorize them.

• ACARA Content Descriptions
• AC9DT10P02
• AC9DT10P03

• 30–50 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Concept Mapping
• 45 min · Pairs

Pair Programming: Schema Design Challenge

Pairs sketch an ER diagram for a social media network with users, posts, and likes tables. They identify primary keys, foreign keys, and normalize to 3NF, then create the database in SQLite. Partners alternate explaining choices to each other.

How does data normalization prevent redundancy and inconsistency?

Facilitation Tip

During the Pair Programming: Schema Design Challenge, circulate and ask teams to explain how their foreign keys prevent orphaned records when one table is deleted.

What to look for

Present students with a poorly designed table containing redundant information. Ask them: 'Identify at least two instances of data redundancy in this table. Explain how this redundancy could lead to data inconsistency when updating records.'

• Understand
• Analyze
• Create
• Self-Awareness
• Self-Management

Activity 02

• Concept Mapping
• 50 min · Small Groups

Small Groups: SQL Query Relay

Divide a sample customer orders database among groups. Each group writes and tests one SQL query type: SELECT with JOIN, INSERT, UPDATE, DELETE. Groups share queries class-wide for peer testing and discussion.

What are the ethical implications of linking disparate datasets together?

Facilitation Tip

For the SQL Query Relay, seed the first incorrect query in each relay so students practice debugging syntax errors under time pressure.

What to look for

Provide students with a simple scenario (e.g., managing a small band's gigs and members). Ask them to: 1. Design a basic schema with at least two tables, including primary and foreign keys. 2. Write one SQL query to list all band members and their instruments.

• Understand
• Analyze
• Create
• Self-Awareness
• Self-Management

Activity 03

• Concept Mapping
• 30 min · Whole Class

Whole Class: Ethical Dataset Linking Debate

Present two datasets: health records and shopping history. Class votes on linking them, then queries the combined schema in SQL to reveal insights. Discuss ethics via think-pair-share.

How would you design a schema to represent a global social media network?

Facilitation Tip

In the Ethical Dataset Linking Debate, provide three concrete design choices per scenario so students ground ethical arguments in technical constraints they have experienced.

What to look for

Pose the question: 'Imagine a government agency wants to link public health data with social media activity. What are the potential ethical concerns regarding privacy and data misuse? How might database design choices impact these concerns?' Facilitate a class discussion.

• Understand
• Analyze
• Create
• Self-Awareness
• Self-Management

Activity 04

• Concept Mapping
• 35 min · Individual

Individual: Normalization Puzzle

Provide unnormalized data on school clubs. Students identify redundancies, create normalized tables, and write SQL to populate them. Submit queries for class database demo.

How does data normalization prevent redundancy and inconsistency?

What to look for

Present students with a poorly designed table containing redundant information. Ask them: 'Identify at least two instances of data redundancy in this table. Explain how this redundancy could lead to data inconsistency when updating records.'

• Understand
• Analyze
• Create
• Self-Awareness
• Self-Management

A few notes on teaching this unit

Start with concrete, messy data sets so students feel the pain of redundancy before learning normalization rules. Avoid introducing second normal form until students have manually cleaned unnormalized tables and timed how long updates take. Research shows students grasp joins better when they design the tables first, so teach schema design before query writing to build intuitive understanding.

Successful learning looks like students designing schemas that prevent redundancy, writing SQL that correctly retrieves related records, and debating trade-offs between normalization and query speed with evidence from their own prototypes. Expect students to articulate why foreign keys matter and how normalization reduces update anomalies.

---

Watch Out for These Misconceptions

• During the Pair Programming: Schema Design Challenge, watch for students treating tables like spreadsheets without primary keys.

  Ask teams to explain how they chose primary keys and what happens when two users share the same username if no key prevents duplication.

• During the Small Groups: SQL Query Relay, watch for students assuming LIKE clauses work the same as search engine keywords.

  Provide a broken query using wildcards and ask groups to fix it by testing with sample data before moving to the next station.

• During the Whole Class: Ethical Dataset Linking Debate, watch for students dismissing privacy concerns because data is anonymous.

---

Methods used in this brief

• Concept Mapping