The CREATE statement is the starting point of SQL's Data Definition Language (DDL). While queries with SELECT read data that already exists, DDL commands build and shape the containers that hold data: databases, schemas, and tables. In this topic you will work through that hierarchy from the outside in — creating a database, organizing objects into a schema, and then defining individual tables with named columns and data types.
This matters in COP4708 because everything you have designed on paper so far — entities, attributes, relationships — eventually has to be expressed as runnable SQL. A well-written CREATE TABLE statement captures your design decisions: what each column is called, what kind of values it may hold, how wide or precise those values are, and which schema the table belongs to. Poor choices here (a text column for a date, an undersized character field, inconsistent naming) are costly to fix once data is loaded.
As you watch, pay attention to three things: the exact syntax and punctuation of a CREATE statement, how the presenter chooses a data type for each column and justifies it, and how fully qualified names (schema.table) are used. Also notice that syntax varies a little between database products such as MySQL, Oracle, SQL Server, and PostgreSQL, so confirm the dialect your course environment uses before you run anything.
A short, focused walkthrough of the CREATE TABLE statement using a worked example. Based on the title and channel, it should show the basic syntax — table name, the list of column definitions, and the data type assigned to each column — and then run the statement to produce a working table.
This is the core subtopic of the lesson delivered concisely, and Database Star is a well-established SQL instruction channel known for accurate, dialect-aware explanations. At under six minutes it gives you a template you can imitate immediately when writing your own column definitions.
This video covers CREATE DATABASE, the command that establishes the top-level container before any tables exist. Given the title and description, expect to see the basic statement, example variations, and likely supporting details such as listing or selecting a database after creating it, demonstrated in MySQL.
It directly addresses the "Creating a New Database" subtopic and sets up the database-schema-table hierarchy, so you understand what a table is being created inside of rather than treating CREATE TABLE as an isolated command.
A longer, project-style video that moves from a completed database design to the SQL code that implements it. Expect a demonstration of translating entities and attributes into CREATE statements, including decisions about table names, columns, and data types, as part of a broader design-to-implementation workflow.
It connects CREATE statements back to data modeling, which is exactly the skill this course builds, and it reinforces best practices for writing CREATE statements by showing them applied to a full design rather than a single toy table.
Together these videos build the practical foundation for the module's outcomes. The CREATE TABLE and design-to-SQL videos directly support MO2 by modeling how to write statements with appropriate column names and data types, and they illustrate DDL's distinct purpose — defining structure rather than retrieving or changing rows — which supports the classification work in MO1. The CREATE DATABASE video establishes the database and schema context in which tables and their constraints live, preparing you for the integrity rules in MO3. Because MO3, MO4, and MO5 extend beyond CREATE into constraints, ALTER TABLE, and DROP/TRUNCATE/DELETE, treat these videos as the base layer and pair them with the module readings and later topics that cover those commands.
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.