Less is best

[ABC123]

What are people's opinions of splitting up detail as much as possible into
more tables?

I am creating a table for employees. I was planning on putting all contact
details into one table, however I am now thinking of doing the following:-

Table1

PKemployeeID
Name
Surname

Table 2

PKemployeeID
FKcontactID
Address
City
Telephone
Email

I will never need to search on people's addresses etc, so would it be best
just to put it all in one?

 

[Joseph Meehan]

What are people's opinions of splitting up detail as much as possible
into more tables?

I am creating a table for employees. I was planning on putting all
contact details into one table, however I am now thinking of doing
the following:-
Table1

PKemployeeID
Name
Surname

Table 2

PKemployeeID
FKcontactID
Address
City
Telephone
Email

I will never need to search on people's addresses etc, so would it be
best just to put it all in one?

Well if they are going to have more than one address - telephone and
e-mail and all three of those are going to be in matched sets, you don't do
it that way.

Start with the idea of everything in the one table (I suggest a MI as
well). Then if you have more than one telephone number that goes in a
telephone table, different addresses means you need an address table same
with e-mail So you can have one name in table A a couple of addresses in
table B and say 6 e-mail addresses in table C.