How databases organise information — Technology, 11–13 years
A database stores many related pieces of information in a structure that can be searched and changed. Tables, fields and links help a system find one useful answer without reading every record from the beginning.
A searchable collection
Imagine a school library catalogue with one row for each book and columns for title, author and shelf. A database does something similar, but can hold millions of records and answer questions quickly. It stores the facts in organised parts so people and programs can add, find, sort or update them.
Why lists are not enough
A small list works for a few books, but a large service may track customers, orders, locations and changes every minute. Separate, messy copies can disagree and take too long to search. Databases were developed to keep related information consistent and make precise questions possible at useful speed.
Finding library books
A catalogue has three records: River, Ana, science; Stars, Leo, history; River, Mia, science. To find science books by title River, the system checks the subject field first, keeps Ana’s and Mia’s records, then checks the title field and returns both River entries. It has filtered the table instead of guessing from the words on screen.
A database is not automatically true
A neat table can look trustworthy, so it is tempting to believe every answer it gives. But a database only searches the information entered into it; a misspelled name, old address or missing record can produce a wrong result. Good systems check data and show when information may be incomplete or out of date.
Where databases appear
Online shops use databases for products, stock and orders. Libraries use them for books and loans; hospitals use them for appointments and records; games use them for players and scores. Whenever a service must remember many connected facts and answer questions about them, a database may be working underneath.
Keep exploring
Other languages
Loading MyLeoNes™…