A database schema is a named logical container that groups related tables, views, indexes, and other objects inside a database. Instead of dumping every table into one undifferentiated space, you can create a schema such as sales or hr and place the objects that belong to that area of the business inside it. Because object names only need to be unique within a schema, two different schemas can each hold a table called ORDERS without conflict.
In this module you will practice the statements that make this work: CREATE SCHEMA to define the container, schema-qualified names such as sales.orders to refer to an object unambiguously, CREATE TABLE statements written inside a chosen schema, and DROP SCHEMA to remove one (with care, since dropping a schema can take its contents with it). Keep in mind that different database systems treat schemas slightly differently — in Oracle a schema is tied to a user account, while in PostgreSQL and SQL Server a schema is a separate namespace you create explicitly — so always check which product you are writing for.
As you watch the videos below, pay attention to two things. First, notice how objects are named and referenced: when does the writer use a bare table name and when does a prefix appear? Second, notice how design decisions — which tables exist and how they relate — naturally suggest which objects belong together, which is exactly the organizational benefit schemas provide.
A walkthrough of Oracle Live SQL, the free browser-based environment for running SQL statements against an Oracle database without installing anything. The video is likely to show how to sign in, open a SQL worksheet, run CREATE and SELECT statements, and browse the objects that belong to your account. Since an Oracle user account is effectively a schema, the tour of your object list is a practical look at what a schema contains.
Database Star is a well-established SQL and database design channel, and this tutorial gives you a no-setup place to practice the CREATE TABLE and schema-qualified naming exercises from this topic rather than only reading about them.
An overview of the database design process, from gathering requirements and identifying entities to defining tables, columns, keys, and the relationships between them. Expect coverage of how related tables are grouped and normalized into a coherent structure before any SQL is written. The result of that process is the logical design that a schema is used to hold.
It supplies the reasoning behind the subtopic on schema benefits for database organization: once you can see which tables form a related group, it becomes clear why you would place them in a named schema together.
These videos support the module outcomes by giving you both a place to practice and a reason to care about structure. The Oracle Live SQL tutorial provides a working environment in which you can type and run the DDL statements the module requires — CREATE TABLE with columns, data types, and constraints (MO2, MO3), ALTER TABLE modifications (MO4), and DROP statements compared against TRUNCATE and DELETE (MO5) — while seeing the resulting objects appear in your own schema. The database design video reinforces MO1 and MO3 by showing how entities, keys, and relationships are decided before DDL is written, which is what the PRIMARY KEY and FOREIGN KEY constraints you code later are actually enforcing. Together they connect the design thinking behind a schema to the DDL commands that build it.
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.