Before you can write SQL that defines a database, you need a clear mental picture of what a relational database actually is. In the relational model, data is stored in tables (also called relations), each table holds rows (records) that represent individual things or events, and each row is made up of columns (attributes) that hold a single piece of typed data. Tables are not isolated: they are connected to one another through shared key values, which is what lets you store a customer once and reference that customer from thousands of orders without repeating the data.
This matters in COP4708 because every CREATE TABLE statement you write in this module is a direct translation of these ideas. A table definition names the relation, the column list fixes the attributes and their data types, and primary and foreign key constraints encode the relationships. Schemas sit above all of this as the organizing container that groups related tables inside a database.
As you watch the videos below, pay attention to three things: the vocabulary (table, row, column, key, schema) and how consistently it is used; how the speakers describe the connection between two tables and the role keys play in that connection; and the trade-offs that make the relational model a good fit for structured, rule-governed data. Those trade-offs will help you understand why SQL's data definition features look the way they do.
An introductory explainer on the relational database model, likely walking through how data is organized into tables made of rows and columns and how separate tables are linked through key values. Expect illustrated examples that build up a small set of related tables and show why splitting data across tables avoids duplication. It should also touch on how SQL is used to work with this structure.
This is the most direct match for the core subtopics — tables, rows, columns, and relationships between tables — and IBM Technology produces accurate, whiteboard-style explainers aimed squarely at newcomers.
A broader look at what a database is: what it does, how it differs from a loose collection of files, and the role of the database management system that sits between users and stored data. It is likely to introduce general concepts such as structured storage, querying, and database organization before narrowing to specific database types.
It supplies the context layer beneath the relational model, which helps when you reach schemas and database organization and need to understand what a database management system is actually managing.
A comparison of relational and non-relational (NoSQL) database approaches, contrasting the fixed table-and-schema structure of relational systems with more flexible document, key-value, or similar models. The video should discuss when each approach fits a given workload and what you gain or give up with each.
Seeing the alternative sharpens your understanding of what is distinctive about tables, defined columns, and schemas — exactly the structural commitments that SQL data definition statements make explicit.
These videos build the conceptual vocabulary that the rest of the module depends on. Understanding tables, rows, columns, and key-based relationships is what makes a logical data model readable as a blueprint (MO2) and what makes CREATE DATABASE and CREATE TABLE statements meaningful rather than memorized syntax (MO3). The treatment of keys and links between tables prepares you to apply primary key, foreign key, and column constraints with an understanding of the integrity they protect (MO4). Seeing how SQL is used both to structure and to retrieve data, and how relational systems differ from non-relational ones, frames the distinction between SQL's data definition and data querying roles (MO1) and gives you the structural grounding needed to connect each design phase to its SQL implementation activity (MO5).
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.