TK Study
HomeLearn step by stepMemoriseKey termsFlashcardsNotesMaster answersPast questionsMultiple choiceMock examPractice & marker

Software Engineering › Key terms › Code patterns › SQL statement structure

SQL statement structure

Code pattern Code patterns

Definition

SELECT fields FROM table WHERE criteria GROUP BY field ORDER BY field ASC or DESC; keyword AS renames a field for display.

Example

SELECT Name FROM Games WHERE Cost > 20 ORDER BY Name ASC

Found in: course specifications, 2025 HSC marking guidelines, sample exam and familiarisation guidelines, school notes, past SDD papers.

Where it is used in the test

Syllabus area: Code patterns.

Question types it can appear in

Where it has appeared in the paper

Programming for the Web (Part A, B, C). Part letters follow each paper’s own layout.

Related past questions

These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

Code pattern: “SELECT fields FROM table WHERE criteria GROUP BY field ORDER BY field ASC or DESC; keyword AS renames a field for display.” Then apply it: SELECT Name FROM Games WHERE Cost > 20 ORDER BY Name ASC

In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.

Technique for the question types

What the marking guidelines and feedback say

2025 HSC Q21 (4 marks): SQL queries

Note: the sample does not filter Category to Software/Hardware (the table is assumed to have only those two). Adding AND (Category = 'Software' OR Category = 'Hardware') is safe. Marker feedback: query must run; quotation marks around data being searched; use OR/AND in WHERE; correct GROUP BY and ORDER BY fields.

Sample exam Q17 (3 marks): SQL (join, filter, order)

An INNER JOIN ... ON equivalent is equally valid. Quote text values. Both tables have a column called Name, so qualify them (Table.Name).

Familiarisation Q12a (2 marks): SQL

The query is not available; the output shown is the MG sample answer.

Worked answers from the marking guidelines

2025 HSC Q21 (4 marks): SQL queries (4 marks): criteria and sample answer

Criteria

4: Correct SQL query that extracts 'Pending' and 'Escalated' jobs for the 'Software' and 'Hardware' categories, counts the jobs for each status in each category, and outputs results in descending order. 3: Addresses most requirements. 2: Some understanding of the problem. 1: Some understanding of SQL or the problem.

Sample answer

SELECT Category, Status, COUNT(JobID) AS Jobs FROM Issues WHERE (Status = 'Pending' OR Status = 'Escalated') GROUP BY Status, Category ORDER BY Jobs DESC

Open the question page

Sample exam Q17 (3 marks): SQL (join, filter, order) (3 marks): criteria and sample answer

Criteria

3: Correct SQL query. 2: Addresses some of the requirements. 1: Some understanding of SQL.

Sample answer

SELECT Products.Name AS 'Product', Suppliers.Name AS 'Supplier' FROM Products, Suppliers WHERE Products.SupplierID = Suppliers.SupplierID AND Products.Producer = 'Yumtreats' AND Products.Mass >= 50 ORDER BY Products.Name DESC

Open the question page

Common mistakes

Marker feedback on other questions of the same type (code and diagram feedback often applies across questions)
  • SQL questions (2025 HSC exam Q21): query must run; quotation marks around data being searched; use OR/AND in WHERE; correct GROUP BY and ORDER BY fields.
General advice
  • Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
  • Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.

Same group in the syllabus: SQL relational and logical operators · SQL calculated aggregate with GROUP BY · CSS rule syntax · XSS JavaScript fragment reading · Shell script pattern

A to Z
← SQL relational and logical operatorsIn Code patternsSubroutine and function (pseudocode) →