
Welcome to Relational Database Design. I'm so glad you're here. Let's get started learn some data architecture!
Let's quickly talk about the case study and the broad view of moving from requirement to database implementation.
Understand the requirements to build the PizzaDB
Here are the software tools I used to create the data architecture diagrams and run the SQL. You don't need these to complete the course, but I though you would like to know what I used.
Understand the various components of a conceptual model and how to read them.
Build a conceptual model based off of requirements.
Learn the overall process we use to move from conceptual model to ER diagram.
Learn about Entity Relationship Diagrams and when to use them.
Database normalization can be really abstract. Before we get into some of the definitions, let's look at a practical view.
You may wonder what's all the fuss about database normalization. Let me show you some good reasons you'll want to understand it.
The three normal forms are guide lines we can used to help use determine how to design tables. The help use know whether columns should be include in a table or should be separated. The forms build upon one another. In order for a table to be in the second form, if must first meet the criteria for the first.
For those that are impatient check out the our Five Minute Guide to Database Normalization within the downloadable resources.
Once a table is in the first normal form, the table is considered a relational database table, and it doesn't contain any repeating values.
To better understand the first normal form, lets go over some examples.
When a table is in the second normal form the table serves a single purpose.
Let's transform our first normal form tables into the second normal form.
Tables in the third normal form have columns that aren't calculated, that is they don't rely on other column values from within the table.
In this lesson we'll transform our tables from 2nd to 3rd normal form.
Learn how requirements, conceptual models, ER Diagrams and normalization fall in place to assist DB design.
Use the conceptual model to create the first draft of our ERD diagram.
Continue to refine the ER diagram by applying database normalization rules.
Use the conceptual model to create the first draft of our ERD diagram.
Continue to refine the ER diagram by applying database normalization rules.
Continue to refine the ER diagram by applying database normalization rules.
Learn about the subset of SQL commands used to create tables.
Use the CREATE TABLE command to define tables and columns.
Learn how to define primary, unique, and foreign key constraints.
Review the script used to create the database and tables based on the ER Diagram design.
This course is perfect if you're looking for entry-level course to learn data modeling and relational database table design.
Its singular purpose is to teach you relational database logical design using simple to understand English. We'll walk though modeling requirements, building the conceptual data model, and logical database model. Finally we create scripts to create the physical tables. If you looking to understand data architecture, then you'll find this course very practical!
Join me as we work through Lou's, the owner of several pizza shops, to model, design and create a database he can use to track is business.
In this Course you will Learn to:
Create a conceptual data model based on Lou's Pizza Shops' requirements.
Use ER (Entity-Relationship) diagrams to model and design database tables and relationships between one another.
Appreciate and design around data modification anomalies.
Identify a properly formed database table.
Answer common interview questions related to relational database normalization and data architecture.
Spot a poorly designed table.
Communicate with others about table design.
Finally understand those confounding normalization rules!
Identify database normalization issues within our design and know how to fix them.
Use an ERD (Entity Relationship Diagram) to create database scripts.
Nothing is worse than
Being excited to learn something new but not knowing where to start.
Wasting time learning the wrong features.
Being overwhelmed with options and not know which to use.
Imagine Having...
Knowledge - Knowing how to quickly understand database design to take your SQL to the next level.
Confidence - Feeling good that you’re on the right track.
Accomplishment - Having a sense of accomplishment that you've learned something most cannot.
Fun - Having fun learning databases!
By the time you’ve completed this course you’ll be able to design and implement relational databases using tables, keys, relationships, and SQL commands in MySQL, PostgresSQL, and SQL Server to meet user and operational needs.