SQL Server the Fun Way: Architect a Movie Theater
This course will provide you with an introduction to Database Architecture. To do this, we will build a database step-by-step for a fictional movie theater. This theater needs to keep track of ticket sales, concession sales, and their own special loyalty program. By the end of this course we will have discussed many topics, including Primary Keys, Foreign Keys, Identity columns, several datatypes and much more.
This course will use Microsoft SQL Server but the core concepts apply to any SQL-based database system.
You should take this course if you are interested in learning Database Architecture concepts. We’ll cover several datatypes and go over when and when not to use them. We’ll cover many different types of tables, including dimension table and history tables.
After you’ve taken this course you will have a basic understanding of how databases fit together and how to think about creating your own database for your future projects.
Introduction and Requirements
This is the introduction lecture for this course.
This explains the basic requirements the Movie Theater wants.
Introduction to Datatypes
Explaining the TinyInt, SmallInt, Int, and BigInt datatypes.
Explaining char, varchar, nchar, and nvarchar datatypes.
Introduction to Keys
Discussing and implementing Primary Keys in tables.
Discussing and implementing Foreign Keys in tables.
Explaining the Date, Time, DateTime and DateTime2 datatypes.
Organizing Movies and Actors
This table stores a list of our Movies.
This table stores a list of our Actors.
This table stores links between our Movies and Actors tables.
Floating Point Datatypes
Explaining the Float, Numeric, Decimal, Money, and SmallMoney datatypes.
Advanced Table Types
Creating the table that stores our ticket prices.
Creating our Employee table and our Employee History table.
Creating the table to store our Customer details.
Creating the table for our Loyalty Program.
Creating the table to store our attendance.
Bonus DIM Date Table
Showing an extra table that is useful in most databases.
Walking through our finished product.