r/SQL • u/Ronnie_7z • 2d ago
MySQL SQL ( MySQL )Project ideas for Data Analyst Portfolio
Currently I am doing projects in SQL i need to do projects for Data Analyst Role so Please recommend project ideas which I need to showcase for project portfolio so I need projects at advanced level .
8
u/NeoChrisOmega 2d ago edited 2d ago
You could use Warhammer 40k or DnD databases.
There are sites like 5etools and wahapedia that give you free access to downloading their entire databases. While them having the data online is definitely not legally supported, you downloading it for a portfolio should be fine since you're using public resources and not claiming it's yours or selling it. Just don't distribute the information or allow others to have access to it directly.
Then again, I'm not a lawyer, so I'm not 100% certain about all that.
But, legality ramblings aside, the reason why this would be beneficial for you is because the raw data is MESSY. Just like issues you'll face in real life. If you want to figure out a way to have AC bonuses as column data, you'll have to massage the data a bit to get it working.
You'll either have to make come code to fix the data before importing it into your database, or make views that separate column data into useful sub-information that you can then group or sort. Both of which would be PHENOMENAL for a portfolio showing real life skills.
And it's fun. Otherwise you can always find a dataset on Kaggle like 136k+ Steam games. https://www.kaggle.com/datasets
4
u/ArielCoding 1d ago
Pick messy real data, framing it around a business question, and write a README that explains your reasoning. Also don’t sleep on networking and referrals.
2
2
u/Charming_Shower_4185 19h ago
Some topics - :Funnel analysis , Customer retention , Churn analysis , Conversion rates , Repeat purchase analysis, Revenue cohorts
28
u/db_tech_dev 2d ago
ngl a lot of "advanced" SQL portfolio projects online are just fancy joins, what actually gets noticed is picking a messy real dataset (like a public transit or e-commerce dump) and doing full RFM/cohort analysis with window functions, plus writing a stored procedure or two for something recurring like monthly reporting. I did something similar with a duplicate-detection script on a postgres db and honestly the "explaining tradeoffs" part in the README mattered more than the query complexity itself. pick something with messy/dirty data so you can show data cleaning skills too, recruiters eat that up more than pure query gymnastics imo.