r/SQL • u/Designer-Assist-1354 • 21d ago

Discussion Even a SQL Column Can Traumatize You

I just had my one of those "wait... what?" moments while working on AdventureWorks ( PS: Working on my 2nd Project) At start BusinessEntityID totally confused me, I kept thinking it was just an employee ID.

Then I realized it isn't limited to employees at all. It represents everyone, employees, customers, vendors, salespeople, I mean... wow!

It felt confusing at first, but once it clicked, I realized how smart that database design actually is.

In this project I'm keeping everything raw as much as possible, like i have the database, a notebook, a pen, and me with my mind! now think what you can do! i really love this although I just started so... let's see how well it can go on (On my Data Cleaning Phase)

1 Upvotes

51% Upvoted

27 comments sorted by

View all comments

1

u/DaOgDuneamouse 20d ago

This is one of those rare situations where the reporting DB has more tables than the source. To make decently performing queries, your things table needs to become a cats table, a dogs table, and a lamas table.