ISYS2120 Chap.1 Database Foundations and Relations
Database Foundations and Relations
This chapter establishes why an organisation uses a DBMS rather than isolated application files. It follows persistent, shared facts into a database whose structure is recorded in a system catalogue. The relational model then separates a stable schema from the changing instance that must satisfy it: tables contain uniformly structured rows, matching values connect facts, and integrity constraints limit valid states.
The final section distinguishes the External, Conceptual and Physical levels and uses data independence to explain why a user view need not change when logical or storage details change. These distinctions matter in early quizzes and in final-examination explanations that ask what a DBMS contributes, not merely what a SQL command does.
What this chapter covers
- 01
Why managed data beats loose files
- 02
Separate data from its descriptions
- 03
Move through three levels of abstraction
- 04
Use data independence as a design test
- 05
Read a relation precisely
- 06
Choose domains before values arrive
- 07
Identify candidate keys from row distinctions
- 08
Protect identity with primary keys
- 09
Link relations with foreign keys
- 10
Place DBMS responsibilities
- 11
Audit a relational design as a whole
Trace linked facts through two relations
- +1Read Supplier and identify the row whose name is North Tools: its linking value is supplier_id S1.
- +1Inspect Product as a separate relation and retain only rows whose supplier_id matches S1.
- +1Project the requested product columns. P10 and P12 remain; P11 is excluded because its supplier_id is S2.
- +1State the computed result relation and preserve both rows even though they share the same supplier.
Key terms
- Database
- A collection of persistent data, usually large enough to support an organisation or a coherent part of one. The database is stored data; the DBMS is the software that manages it.
- DBMS
- A software package designed to store and manage one or more databases while allowing shared access from multiple application programs.
- Metadata
- Information about data, including its structure, origin or obligations attached to it. A DBMS can store metadata alongside the operational data it describes.
- Data
- Facts that can be recorded, matter to users and need to persist beyond a temporary computation.
- System catalogue
- The database-held description of schema objects, including table names, column names, datatypes and constraints.
- Relation
- A named table in the relational model whose rows have the same attributes. Mathematical relations have no duplicate rows and no meaningful row order.
- Schema
- The comparatively stable description of a database's structure: its tables, columns, datatypes and integrity constraints.
- Instance
- The database contents at one particular time. Each update changes the instance, and every valid instance must fit the schema.
- Physical level
- The level that describes how data is stored in files and other storage structures. It sits below the Conceptual level in the three-level architecture.
- Data independence
- Protection of one database level from changes at a lower level. Logical independence protects user views; physical independence protects the conceptual design from storage changes.
Database Foundations and Relations FAQ
What problem does a database management system solve?
A DBMS coordinates persistent organisational data with a catalogue, query processing, integrity, controlled sharing, recovery and storage services. Unlike a loose file collection, it gives applications a common structure and a place to enforce rules.
Where is metadata used in a relational database?
Metadata records the schema: relation and attribute names, domains, keys and constraints. The DBMS catalogue uses those descriptions to interpret stored values, validate statements and explain what a column means beyond its heading.
Why are there several levels of database abstraction?
External views serve particular users, the Conceptual level describes the shared logical structure, and the Physical level handles storage. Separating them limits the changes that applications must absorb when implementation details move.
How do I identify a candidate key in this unit?
Use the unit definition: any combination of columns that can distinguish the rows is a candidate key. Test the proposal against every permitted database state, not only the displayed sample, then identify which candidate the schema declares as its primary key.
What should I inspect when a relational design looks plausible?
Check relation meaning, attribute domains, candidate keys, primary-key stability, foreign-key targets and the invalid states each constraint rejects. Then test duplicates, missing values and changed descriptive attributes with a small counterexample.
Exam move
Revise this chapter as a set of contrasts. From memory, explain data versus database versus DBMS, schema versus instance, and Conceptual versus Physical level; then give one organisational example for each side. Redraw the Supplier and Product relations and point to the matching values that encode their connection. Next, invent one invalid instance for every integrity rule and say precisely why the schema rejects it.
For architecture questions, begin at the user's External view, move through the Conceptual description, and finish at Physical storage; name which kind of data independence insulates each boundary. Use short closed-book retrieval because the final examination requires both vocabulary and reasons.
Keep a correction log with three columns: confused pair, smallest distinguishing example, and the sentence you would write under time pressure. End by explaining why shared, catalogue-described data avoids the inconsistency risk of separate application files.
Working through Database Foundations and Relations in ISYS2120? Sia is AskSia’s AI Information Technology tutor — ask any ISYS2120 Database Foundations and Relations question and get a clear, step-by-step explanation grounded in how ISYS2120 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
