Too many columns in one table - is this a good normal form?

Question

A normalized table should have fewer number columns and may have as many reference fields as possible. Is it correct? Is there a connection between the number of columns and a good normalization process?

Answer 1

You should follow the principles of normalization, and not care about the large number of columns in the table. Business requirements will manage the objects, their attributes and their relationship, and the absolute number is not "correct."

Answer 2

Is there any correlation between the number of columns and the good normalization process?

, . 3NF , , ,

, ( ).

, () , , , - .

Answer 3

, , , . : -

CREATE TABLE Person
    Person_ID int not null primary key,
    Forename nvarchar(50) not null,
    Surname nvarchar(50) not null,
    Username varchar(20) null,
    PasswordHash varchar(50) null

, , , Username PasswordHash NULL. , 1 2 , .

User Username PasswordHash " " Person.

, , null , , null. , .

Edit

(. ) , -, " "

Answer 4

@ocdecio, , , , , , . , , . , , , . , , "".

Answer 5

. - , . .