Database Table Normalization

Hi all,

This is actually a pretty stupid question, but somehow I need an answer from you experts.

We are currently building a web application using ASP.NET, and it simply manages contact information, like outlook. Contact information include first name, last name, birthday, etc. It also tracks address, phone number, and email. Here come the problem.

We allow only one address, 4 phone numbers and an email for each contact. When we building the database table, should we create 6 fields to contain all the information or should we create address, phone, and email table and then create the relationship between them.

Will the first method speed up the performance? Or the second method is the proper way?

I need some pros and cons on each

Thanks so much for your opinion

Sam