Build a Netflix Database. Movies, title, dates, actors, etc. perform searches. Ok add Genres. Ok add TV. seasons and series. ok how can you reduce the number of tables? ok perform more complex searches. JOINS, GROUP BY, FK, etc. Note: The interviewer steadily made additional requests for changes in the database to add more features. At one point the interviewer asked to merge two linking tables into a single table with a single field storing the FK's from two different tables (ie bad database integrity). I complied because I thought the point was to make a difficult complex query example (which it did). We were rushed at the end and I didnt get to circle back and point out why that is sooo bad. Later they said I had a bad database design...which seemed strange to me since I didn't even think I was doing a database design. Call everything out, I should have.
