A relational database organises data into tables, with rows representing individual records and columns representing attributes of those records, connected through shared keys. SQL (Structured Query Language) is used to interact with these databases: SELECT retrieves data, INSERT adds new records, UPDATE modifies existing records, and DELETE removes records, often filtered using a WHERE clause to target specific rows.
Example
A simple query like SELECT name FROM students WHERE year_level = 12 would retrieve the names of every student in a "students" table whose year_level column equals 12 — a basic but powerful way to extract exactly the data needed from a much larger table.
Key terms
Relational database:
A database organising data into related tables of rows and columns.
SQL:
Structured Query Language, used to interact with relational databases.
WHERE clause:
A part of an SQL query used to filter results based on a condition.
Questions
1. A relational database organises data into:
Tables of rows and columns
A single unstructured block of text
Nothing organised at all
Only images, with no text data
2. SQL stands for:
Structured Query Language
Simple Query Logic
System Quality Layer
A term unrelated to databases
3. SELECT is used to:
Retrieve data
Delete an entire database permanently
Only add new records, with no other function
Format text, with no connection to data retrieval
4. INSERT is used to:
Add new records
Retrieve existing records only
Delete every record in a table
Format the appearance of a table
5. DELETE is used to:
Remove records
Add new records only
Retrieve records only
Rename a table
6. A WHERE clause is used to:
Filter results based on a condition
Delete an entire table with no filtering
Rename a column
Format the database's appearance
7. In a database table, a row represents:
An individual record
A single column heading only
The entire database at once
Nothing meaningful
8. The query SELECT name FROM students WHERE year_level = 12 would retrieve:
The names of students where year_level equals 12
Every single record in the database, with no filtering
Only the year_level column, with no names
Nothing at all, since this query is invalid
9. UPDATE is used to:
Modify existing records
Add brand new records only
Delete an entire table
Rename an entire database
10. Why might a WHERE clause be considered essential when using UPDATE or DELETE, rather than optional?
Without it, the command could unintentionally affect every single record in the table, not just the intended ones
A WHERE clause has no effect on how UPDATE or DELETE commands behave
UPDATE and DELETE commands always automatically target only a single specific record
WHERE clauses are only ever used with SELECT, never with UPDATE or DELETE
11. Why might data be organised into multiple related tables (like "students" and "grades") rather than one single giant table?
Splitting related data into separate tables reduces repetition and keeps the data more organised and manageable
A single giant table is always more efficient and organised than multiple related tables
Splitting data into multiple tables always makes a database less functional
Relational databases never use more than one single table for any purpose
12. A shared "key" connecting two tables (like a student ID appearing in both a "students" and "grades" table) allows:
Related data to be linked and queried together across tables
The two tables to become completely identical to each other
Data to be permanently duplicated with no connection between tables
Nothing meaningful; keys serve no functional purpose
13. Why might businesses rely on relational databases (rather than spreadsheets alone) to manage large amounts of structured data?
Databases handle large volumes of structured, related data more efficiently and reliably than spreadsheets, especially with many simultaneous users
Spreadsheets are always superior to databases for managing any amount of structured data
Relational databases have no practical advantage over spreadsheets in any business context
Databases and spreadsheets are functionally identical with no meaningful difference
14. Why might poorly written SQL queries (like an UPDATE with no WHERE clause) pose a serious risk in a production system?
They could unintentionally modify or delete large amounts of real, important data all at once
Poorly written queries never have any real consequences in a production database system
SQL queries always automatically prevent any unintended, large-scale changes to data
Production systems are always completely immune to any risk from database queries
15. Why might understanding SQL be considered a valuable skill across many different careers, not just software development?
Many roles in business, research and analytics involve querying and interpreting data stored in relational databases
SQL is only ever useful to professional software developers, with no application elsewhere
Understanding SQL provides no practical value outside of a formal computer science context
Data querying skills are never relevant to roles in business or research
16. Why might a database administrator create backups of a database before running a major UPDATE or DELETE operation across many records?
It provides a way to recover the original data if the operation has unintended consequences
Backups are never necessary before running any kind of database operation
UPDATE and DELETE operations never have any risk of unintended consequences
Recovering original data is impossible once a database operation has been run
17. A column in a database table represents:
An attribute of the records in that table
An individual record itself
A completely separate, unrelated database
A single row only, with no wider table structure
18. The query SELECT * FROM students would retrieve:
All columns and rows from the students table
Nothing at all, since this query is invalid
Only a single row from the table
Only the table's name, with no actual data
19. Why might a "key" field (like a unique student ID) be required in a database table, rather than relying on names alone to identify records?
Names can be duplicated between different people, while a unique key reliably identifies exactly one specific record
Names are always guaranteed to be completely unique, making a separate key field unnecessary
Unique keys serve no functional purpose in a relational database
Every database table is required to use names, and only names, to identify each record
20. Why might querying a well-structured relational database often be far faster than searching through an unorganised collection of files for the same information?
Structured tables and indexing allow the database to efficiently locate and retrieve specific data rather than searching everything sequentially
Structured databases are always exactly as slow as searching through unorganised files
Indexing and table structure have no effect on how quickly data can be retrieved
Searching unorganised files is always faster than querying a structured database
21. Why might a database designer normalise a database (organising data to minimise redundancy across tables) rather than storing all information in one large table?
Reducing duplicated data lowers the risk of inconsistencies when information is updated in only one of several places it appears
Storing all information in a single large table always eliminates any risk of data inconsistency
Normalisation has no meaningful effect on data consistency or redundancy in a database
A single large table is always the most reliable and efficient way to organise any data set
Answer key (parent copy)
1. Tables of rows and columns
2. Structured Query Language
3. Retrieve data
4. Add new records
5. Remove records
6. Filter results based on a condition
7. An individual record
8. The names of students where year_level equals 12
9. Modify existing records
10. Without it, the command could unintentionally affect every single record in the table, not just the intended ones
11. Splitting related data into separate tables reduces repetition and keeps the data more organised and manageable
12. Related data to be linked and queried together across tables
13. Databases handle large volumes of structured, related data more efficiently and reliably than spreadsheets, especially with many simultaneous users
14. They could unintentionally modify or delete large amounts of real, important data all at once
15. Many roles in business, research and analytics involve querying and interpreting data stored in relational databases
16. It provides a way to recover the original data if the operation has unintended consequences
17. An attribute of the records in that table
18. All columns and rows from the students table
19. Names can be duplicated between different people, while a unique key reliably identifies exactly one specific record
20. Structured tables and indexing allow the database to efficiently locate and retrieve specific data rather than searching everything sequentially
21. Reducing duplicated data lowers the risk of inconsistencies when information is updated in only one of several places it appears