How sharifathar/netflix-shows-and-movies-sql works
Project type and purpose
• This is a data-analytics/reporting project. It ingests the Netflix titles dataset (CSV), loads it into MySQL, runs SQL analyses, and presents results via Tableau (and occasionally Excel).
• Its goal is to uncover insights (top/bottom titles, decade distribution, age certifications, genre frequency) and display them in a dashboard.
File structure
• Top-level files:
• Netflix_SQL_Analysis.sql – contains all the SQL queries/analysis.
• README.md – explains business problem, tools, methodology, sample queries & results.
• No application code, no services beyond the database and BI tools.
README for additional insights
• Tech stack: MySQL for storage/analysis; Tableau for visualization; Excel for ad-hoc checks.
• Data source: “titles.csv” from Kaggle (≈82k rows).
• Core workflow: ETL → SQL analysis → Tableau dashboard.
Main components and their relationships
a. Data Source (CSV file on disk or object store)
b. ETL/Import tool (could be MySQL’s LOAD DATA INFILE or a script in Excel)
c. MySQL Database
d. SQL Analysis Layer (the .sql script hosted in code repo or SQL client)
e. BI/Visualization Layer (Tableau Desktop/Public)
f. Stakeholders (Netflix data consumers, decision-makers)
Interactions:
• CSV → ETL → MySQL
• SQL Analysis <→> MySQL
• Tableau <→> MySQL (live or extract connection)
• Excel ↔ MySQL (ad-hoc data pulls)
Architectural patterns and principles
• Decoupling of layers: storage (MySQL) separated from compute (SQL scripts) and presentation (Tableau).
• Reproducibility: all analysis queries are codified in Netflix_SQL_Analysis.sql.
• Break out the MySQL component into schema (shows_movies.titles) and connection ports (3306).
• ETL step (LOAD DATA, any pre-processing in Excel).
• Under “SQL Analysis,” call out key query groups (IMDB ranking, decade counts, certification impacts, genre frequency).
• In the Tableau block, note dashboards, filters (genre selector, decade slicer, certification view).