@mavenanalytics: If every query you write needs 4 or 5 joins, that's not a you problem. That's a data modeling problem. ⚙️ Transactional databases are built to quickly record data and avoid redundancy, not to answer analytical questions. The fix? A star schema. Same question, one join, clean and readable. Find the full video on our YouTube channel and the Analytics Engineering 101 course at Maven Analytics, both linked in bio! #DataModeling #SQL #StarSchema #AnalyticsEngineering #DataEngineering #DataTok #TechTok #LearnOnTikTok
You’re missing the context on OLTP vs warehouse. Analytical queries shouldn’t be on your OLTP data source where relational models make sense. The data should be migrated to a warehouse where the star schema model makes sense for analyzing.
2026-08-27 13:08:36
1
Viktor :
Joins are not the problem. Relational databases were literally built to make joins work efficiently
2026-07-12 22:55:00
95
yes daddy 😘 :
then lets forget about normalization 🤣🤣🤣
2026-07-18 03:57:58
14
junkforpdp :
Ever heard of a view?
2026-07-12 22:09:46
16
Colin The Zombie :
total nonsense. relational databases are hardwired to handle multiple joins effectively and efficiently. Its how you design that counts.
2026-07-19 13:57:59
24
Hector :
The star schema you just posted is also joining to take five joins
2026-08-21 07:04:18
3
Orangeeena :
This is warehousing schema definition. Not transactional
2026-08-07 19:14:46
0
Bjorn_ :
so how would I use one join to join all the shown dimensions and fact table together in that star shema? 🤣
2026-07-19 18:47:27
2
Brian :
This is totally not true
2026-08-21 22:07:07
1
davidforck :
the problem: select * from all the tables joined together
2026-08-18 21:01:40
2
TimelineJumper :
your star schema diagram had 5 joins. Regardless, it's the best analytics database approach. the magic happens in the ETL to get it there.
2026-07-14 04:47:41
12
Michael Cross :
yea so this is defs not how life works. especially since the report requests change basically daily
2026-07-31 18:26:22
2
Mark J :
Where have you been all my life!? I have been saying this for years!
2026-07-30 02:58:58
1
Gen :
My 10 join query that runs in 2s laughing at the back … yeah star schema, stored procedure ETL and then do bronze , silver , gold and 4 hours delay… what could go wrong.
2026-07-19 18:37:37
4
Big Fatpp :
4/5 is hardly alot
2026-07-18 17:22:12
3
omghiyou :
star schema doesn't solve everything and it can actually cause more issues 👍🏼
...
views is what you need for reporting while keeping data modeling efficient as to minimize data storage costs
2026-08-02 19:23:05
2
Hehe Wu :
How do the star schema deal with when dim table changes eg customer change address part year?
2026-08-11 06:56:43
1
trex :
One join? Isn’t there a join per dimension table?
2026-07-19 14:01:29
6
keone_00 :
ever heard of a normalized database?
2026-07-11 00:48:52
16
Wafsfr_ :
facing this exact problem currently at some point I had 7 joins ita crazy😔
2026-07-16 17:51:37
1
mystrymo :
Joins are not a problem until the amount of data retrieved exceeds the hardware capacity I.e., memory and disk space. Denormalization is useful but it can limit the different types of queries that can be performed. Thus, proper data modeling is the key to success
2026-08-14 00:44:25
1
supersonic :
Don't force a user facing application"s database to run like this for the sake of analytics
2026-07-13 01:13:21
3
Gurkin 71 :
And how does the data get into the star schema? It can't be born there or your OLTP has got big problems.
2026-08-20 10:18:06
1
Felipe Mathias :
Not a single join, is a single join for dimension lol we use denormalized tabela
2026-07-18 23:06:01
1
fataxe :
Hmmm, no.
2026-07-10 20:25:56
4
To see more videos from user @mavenanalytics, please go to the Tikwm
homepage.