· intermediate
Database Design
Decide how data should be stored before you query it. Keys, normalisation, constraints and indexes, and the trade-offs each one makes on your behalf.
Written in house, from the work rather than from a syllabus. Every example is one we would use ourselves, and every exercise is checked against the same engine that grades your answer.
What you’ll learn
- Choose primary keys and understand what identity means
- Model one to many and many to many relationships
- Normalise a table and explain what each step prevents
- Use constraints so the database enforces your rules
- Reason about when an index helps and what it costs
- Write DDL to create and alter tables safely
Before you start
- · SQL Foundations and Joining Data in SQL
- · No experience creating tables required