The relational model describes data using a small number of precisely defined pieces. A relation is a set of tuples over a fixed set of attributes; informally, we draw it as a table, where each row is a tuple and each column is an attribute. Each attribute is associated with a domain — the set of permitted values for that column — and the relation schema names the relation and lists its attributes (and their domains). Because a relation is formally a set, there are no duplicate tuples and no inherent ordering of rows; column order is likewise unimportant once attributes are named.
These definitions matter for everything else in this module. Functional dependencies, candidate keys, attribute closure, and normalization are all stated in terms of attributes and the tuples of a relation, so being comfortable moving between the picture (a table) and the formalism (a set of tuples over attributes with domains) is the prerequisite for the rest of the course.
The videos below approach these ideas from a practical, industry-facing angle. As you watch, deliberately translate the vocabulary you hear — table, row, column, field, data type, key — into the formal terms relation, tuple, attribute, domain, and relation schema. Note where the informal presentation differs from the strict set-theoretic definition (for example, treating tables as ordered lists of rows), and be ready to state the formal version yourself.
An introductory overview from IBM Technology explaining what a relational database is: data organized into tables made up of rows and columns, with keys used to relate tables to one another. Based on its title and description, it likely walks through a simple example schema and touches on SQL as the language used to query such data. It is a short, whiteboard-style explainer aimed at newcomers.
It is the most direct match for the core subtopics — tables, rows, and columns — from a well-regarded technical producer, and it gives you the everyday vocabulary you will map onto the formal terms relation, tuple, and attribute.
A comparison video that contrasts relational databases with non-relational (NoSQL) alternatives such as document, key-value, and other flexible-schema stores. Expect discussion of fixed schemas and structured tabular data on the relational side versus looser, schema-on-read structures on the other, along with trade-offs in consistency, flexibility, and typical use cases.
Seeing what the relational model is not sharpens your understanding of what a relation schema actually commits you to — a fixed set of attributes, each drawn from a declared domain.
A tutorial from Lucid Software on building entity relationship diagrams from scratch, covering entities, attributes, and cardinality as stated in its description. It introduces the notation used to sketch what data you intend to store before writing any schema, with attributes attached to entities.
It reinforces the notion of attributes as the named, typed properties that make up a schema, and connects the abstract relation schema to the design diagrams you will encounter when modeling data.
Together these videos build the vocabulary and intuition that MO1 requires: the IBM overview grounds relations, tuples, and attributes in concrete tables, rows, and columns; the relational versus non-relational comparison highlights why a fixed schema with defined domains is a defining feature of the relational model; and the ERD tutorial reinforces attributes as named properties of a schema. None of the videos covers functional dependencies, Armstrong's Axioms, attribute closure, or anomaly analysis (MO2 through MO5) — those are developed in the module readings and exercises — but the precise understanding of attributes, tuples, and relation schemas you take from these videos is exactly the foundation on which those later outcomes are stated and solved.
These videos were chosen from YouTube on October 2, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.