MSSQL database optimization, database structure

Question

Database

good afternoon,
actually a subject - what database structure to choose?

• 1. one large table that includes all fields (first name, last name, TIN, penny, address, biography, profile, picture, password, login, mail, etc., etc.)
• 2. several tables User_resume (biography, resume url, photo url), User_login (login, password, salt), User_detail (pence, inn, address, etc.)

What is the fundamental difference between these structures? Which option will be more productive? when selecting for example select bio, resume_url, foto_url from User_resumeand select bio, resume_url, foto_url from ONE_BIG_TABLE?
and still the combined from different small tables select t1.bio, t1.resume_url, t1.foto_url, t2.login, t2.password, t2.salt from User_resume as t1 inner join User_login on t1.user_id = t2.user_id as t2
and select bio, resume_url, foto_url, login, password, salt from ONE_BIG_TABLE?

Answer 1

1.
I don't understand how you plan to win in the second case.
There are more indexes, more internal queries, worse caching, and so on.
If you really think about optimizing giant tables, then there is partitioning.