2.1 What a Database Is: Data vs Information

ICDL Using Databases Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About the ICDL Using Databases Module How the Module Is Tested & How to Use This Guide

2 Understanding Databases

2.1 What a Database Is: Data vs Information 2.2 How Databases Are Organised: Tables, Records, Fields 2.3 Data Types, Field Properties, Primary Keys & Indexes 2.4 Relationships & Referential Integrity (Concepts)

3 Using the Application

3.1 Working with Databases 3.2 Common Object Tasks: Objects, Views, Navigation, Sorting

4 Tables

4.1 Records: Adding and Editing Data 4.2 Table Design: Fields, Data Types, Properties, Validation, Keys, Indexes 4.3 Table Relationships: One-to-Many & Referential Integrity

5 Retrieving Information

Search & Filters Building Queries: Single/Two-Table, Criteria & Comparison Operators Advanced Query Criteria: Logical Operators, Wildcards, Editing & Running

6 Forms

6.1 Creating and Using Forms

7 Outputs: Reports, Export & Printing

Reports: Creating, Grouping & Summaries Exporting Data: Spreadsheet, Text, CSV, XML & PDF Printing Tables, Forms, Queries & Reports

2.1 What a Database Is: Data vs Information

Key Takeaways Explain This Topic AI

A database is an organised collection of related data structured for efficient storage, retrieval, and updating.

Data is raw, unprocessed facts; information is data that has been processed into a meaningful, useful form.

Changes made to records in a database are saved automatically, unlike edits in a word-processing document.

Large-scale databases power everyday systems such as social networks, airline bookings, government records, hospitals, and banks.

A database differs from a spreadsheet mainly through its use of multiple related tables, which minimises data duplication.

Last updated: July 2026

A database is one of the most common tools in modern computing, yet many people who use one every day have never had to define exactly what makes it a database rather than, say, a spreadsheet or a folder of documents. This section covers ICDL Using Databases skill set 1.1: what a database is, how data differs from information, how database changes are saved, and where large-scale databases show up in daily life.

What a Database Actually Is

A database is an organised collection of related data, structured so that it can be efficiently entered, stored, retrieved, sorted, and updated. The key word is organised . A database does not simply hold data — it holds data according to a defined structure (tables made up of records and fields, covered in the next section) so that both people and software applications can reliably find, filter, and reuse exactly the information they need.

Think of a physical library. Books are not stacked randomly; they are catalogued by subject, author, and call number so a librarian — or a computer system — can locate any title in seconds. A database applies that same organising principle to digital data: customer lists, product catalogues, medical histories, exam results, and countless other collections of related facts.

Data vs Information

The ICDL syllabus draws a precise distinction between data and information , and this distinction is a favourite exam topic.

Data is the raw, unprocessed facts stored in the database — individual numbers, words, dates, or codes that, by themselves, may not mean very much. A single field value such as 82 or 2026-03-14 is data.

Information is what results once that data has been processed, organised, calculated, or presented in a way that is meaningful and useful to the person reading it. Turning the raw score 82 into the statement "the class average exam score is 82%" turns data into information.

In short: data goes in, information comes out. A database's whole purpose is to store data efficiently so that queries, forms, and reports can transform it into useful information on demand — themes covered later in this guide when you build queries and reports.

How Database Data Is Stored and Saved

Unlike a word-processing document, where you must remember to save your work after every change, a database behaves differently. All the data in a database is stored inside its tables, and in most database applications — including Microsoft Access, on which this ICDL module is based — changes to a record (adding, editing, or deleting data) are saved automatically as soon as you move away from that record. You do still need to save the overall database file to a chosen location the first time you create it, but day-to-day edits to records do not require a manual "Save" step the way a document does.

Common Real-World Uses of Databases

Large-scale databases power a huge share of the systems people rely on every day. The ICDL syllabus specifically expects you to recognise examples such as:

• Sector Example use of a database
• Social networking Storing user profiles, friend/connection lists, posts, and messages
• Travel and airlines Managing flight schedules, seat availability, and passenger bookings
• Government Maintaining citizen records such as identity documents, licences, and tax records
• Healthcare Storing patient records, treatment history, and hospital appointment schedules
• Banking Managing customer accounts, balances, and transaction histories

Each of these systems needs to handle enormous volumes of related data, support many simultaneous users, and retrieve accurate results in seconds — exactly what a well-structured database is designed to do.

Database vs Spreadsheet

A spreadsheet and a database can both hold rows and columns of data, which is why beginners sometimes confuse the two. The ICDL syllabus expects you to understand why a database is the better tool for related, multi-subject data.

• Feature Spreadsheet Database
• Structure One flat grid (or a few loosely connected sheets) Multiple related tables, each covering one subject

Duplication Repeated data is common (e.g., a customer's address typed on every order row) Related tables minimise duplication (an address is stored once and linked)

Data integrity Little built-in control over what can be typed into a cell Field properties and validation rules can restrict and check entries

Relationships No real concept of linking separate subjects together Relationships connect tables (covered in section 2.4)

Best suited for Quick calculations, small lists, one-off analysis Large volumes of structured, related data accessed by many users

For the Exam

Remember the core distinction: a database is an organised, structured collection of related data, information is processed data, and databases outperform spreadsheets specifically because related tables avoid repeating the same data over and over. These ideas set up everything else in this chapter — including how tables, records, and fields fit together, which is the subject of the next section.