[8:42 AM, 11/28/2016] +91 96467 74646: ec ke database mai name phone jaisi cheezein seperate kyun rakhi hain organiser and sponsor ki...dono user table mai store ki jaa sakti thi na...aise alag fields alag alag table mai kyun?
[8:42 AM, 11/28/2016] +91 96467 74646: Oh.. Tooooo many reasons

Because inline fields call hoti hai saari whenever accessing a table row

User table ka purpose authentication hai bas

Auth k time user ka phone number and name kyu chaiye?

And relations pollute honge inline storage se

User has Details..  Details can be different for each type of user. To sparsing avoid krni chaiye jaha bi ho ske.

Future proofing bi ho gyi in case a new type of authentication or user type is introduced

Fake,  inactive, useless users detect krna easy hoga aage jake if alag details alag tables me hai..

ML se train kra ja skta hai for a specific user type for better insights

Finally.. Business sense nhi banta credentials, auth mechanism k sath personal info rakhne ka... Purpose alag hai tables ka.. To alag hi hone chaiye


Decoupling allows you to treat every table as an independent data set. So while analysing one table,  you don't need unnecessary dependencies of other tables..

But agar aggregate level pe bi chaiye ho to tables can always be joined. Ulta nhi hota easily