Skip to main content
Northern IrelandDigital TechnologySyllabus dot point

How is data organised in a database, and how are records found, validated and kept accurate?

Describe how a database organises data into tables, records and fields, explain the role of data types, primary keys, queries, sorting and validation, and outline the benefits of a database over a flat file.

A CCEA GCSE Digital Technology answer on database applications, covering tables, records, fields and data types, primary keys, queries, sorting and searching, validation and verification, and why databases are used.

Generated by Claude Opus 4.811 min answer

Reviewed by: AI editorial process; not yet individually human-reviewed

Have a quick question? Jump to the Q&A page

Jump to a section
  1. What this dot point is asking
  2. Tables, records and fields
  3. Data types and primary keys
  4. Searching, sorting and querying
  5. Validation and verification
  6. Why this matters

What this dot point is asking

A database is software for storing large amounts of structured data so it can be searched, sorted and kept accurate. This part of Unit 1 expects you to describe how data is organised into tables, records and fields, explain data types, primary keys, queries, sorting and searching, and validation, and say why a database is better than an unstructured store. Databases sit behind almost every system you meet, from a school's pupil records to an online shop, so the vocabulary here recurs throughout the course.

Tables, records and fields

Data in a database is held in tables. A table is a grid, and the way it is divided up gives the three core terms you must know.

So a table of pupils has one record per pupil, and each record contains the same fields, such as Pupil ID, Forename, Surname, Date of Birth and Form. Reading down a column gives all the values of one field; reading across a row gives one complete record.

Data types and primary keys

Each field is given a data type that controls what kind of value it can hold and how it is stored. Common data types include text (for names and addresses), number (for quantities and prices), date or time, and Boolean (a yes/no or true/false value). Choosing the correct data type keeps data consistent and lets the database sort, calculate and validate correctly; for example, storing a date as a date type allows it to be sorted into chronological order and used in age calculations.

The primary key matters because it guarantees that records can always be told apart, even when other fields hold the same values, and it is used to link tables together in larger databases.

Searching, sorting and querying

The power of a database is how quickly it finds and organises data.

A query searches the database and returns only the records that meet stated criteria, for example all customers who live in Belfast, or all orders placed after a given date. Sorting arranges records into order on a chosen field, such as alphabetical by surname or by price from low to high. Together, querying and sorting let a user pull out and present exactly the information they need from a very large store.

Validation and verification

Keeping the data accurate is essential, and two different processes help.

Validation is an automatic check that data is sensible and follows the rules before it is accepted. Common validation checks are a range check (a number lies between limits, such as an age from 0 to 120), a presence check (a required field is not blank), a format check (data matches a pattern, such as a postcode), a length check (the right number of characters, such as a phone number) and a type check (the value is the correct data type, such as a number). Verification is checking that data has been entered correctly and matches the original source, for example by typing a password twice or proofreading against a form.

The crucial difference is that validation checks data is reasonable, while verification checks it is accurate. Validation cannot catch a sensible but wrong value: a correctly formatted but incorrect date of birth passes validation, so verification is still needed.

Why this matters

Databases are how organisations store and manage information at scale, and the same structure underlies the database practical work and links to data protection, where personal data must be kept accurate and secure. Understanding fields, records, keys, queries and validation lets you reason about almost any information system you meet in the unit.

Exam-style practice questions

Practice questions written in the style of CCEA exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.

CCEA-style (Unit 1)3 marksDefine the terms field, record and primary key as used in a database.
Show worked answer →

A field is a single item or category of data stored about something, such as Surname or Date of Birth; it is one column of a table (1 mark).

A record is a complete set of fields about one person or item, such as all the details of one pupil; it is one row of a table (1 mark).

A primary key is a field that holds a unique value for each record, so that no two records can be confused; it identifies a record uniquely, for example a pupil ID number (1 mark). A strong answer makes clear that a field is one item, a record is a group of fields about one thing, and a primary key is the field that uniquely identifies each record.

CCEA-style (Unit 1)4 marksA doctors' surgery stores patient details in a database. Explain two validation checks that could be applied to the data entered, giving an example field for each.
Show worked answer →

Any two suitable checks, each tied to a field, earn the marks (2 marks per check: one for naming and describing it, one for a valid example field).

A range check makes sure a number falls between sensible limits, for example a patient's age must be between 0 and 120 (1 mark for the check and description, 1 mark for the field).

A presence check makes sure a required field is not left blank, for example a surname must be entered (1 mark plus the field). Other acceptable checks include a format check (a postcode must match the correct pattern), a length check (a phone number must have the right number of digits) and a type check (an age must be a number). The check must be matched to a field where it makes sense. A common error is to confuse validation with verification, which is checking that data was entered correctly rather than that it is sensible.

Related dot points

Sources & how we know this