Movie Relational Database

This project serves as a testament to my proficiency in relational database design and SQL. It showcases my ability to translate complex data requirements into well-structured relational databases, create Entity-Relationship (ER) models, and efficiently manage database privileges.

Highlights:

Robust Relational Database Design: I have demonstrated a keen understanding of database architecture by designing robust relational databases. These databases efficiently store and organize data, facilitating easy retrieval and analysis.
Entity-Relationship (ER) Modeling: My project includes the creation of ER models that serve as a visual representation of the database's structure and relationships. These models play a pivotal role in ensuring data integrity and guiding the database design process.
SQL Proficiency: The project underscores my proficiency in SQL, the language of choice for interacting with relational databases. I have adeptly crafted SQL queries, statements, and procedures to manipulate, retrieve, and manage data, ensuring optimal database performance.
Privilege Management: Privileges are a cornerstone of database security, and I have skillfully managed them to ensure that data access and modification are restricted to authorized users. This enhances data security and integrity within the database system.

The Dataset

I have chosen a set of four different datasets, based on Movies and TV shows, involving four different hosts, being Netflix, Amazon Prime, Hulu and Disney.

All four of these datasets are of the same format, and consist all the Movies and TV series that are being hosted by these hosts up until the year 2021. The datasets illustrate the names, directors, actors, genres, hosted country, show release date, duration, rating and a short description for each of their Movies / TV Shows.

I was able to concatenate these four datasets into one. Which gives us the base dataset we will work from, which will be in the structure of appendix A.

Appendix A: Snippet of original concatenated dataset

We will be using most entities from the original dataset, which is currently modelled as illustrated in appendix C.

Appendix C: ER diagram of original dataset

ER Modeling

Currently our data is in no Normal Form, and all data is presented in a single entity, indicated in appendix C.

Modeling cardinality from our normalised model, as well as identifying what our Primary and Foreign keys would be, illustrated in appendix F1. This model would be straight forward to implement into an SQL Database, as illustrated in appendix G.

Appendix G: ER model showing cardinality and PK’s / FK’s

Building database

In this stage we will be creating our SQL database, and illustrate how we populate as well as query our database for answering our predefined questions.