hi.

i need some opinions on a certain matter...

normally, i create an employee table containing:

employee ID
first name
middle initial
last name
nationality
birthday
age
home address
home phone
mobile phone
email address
employment status
date started work
salary
civil status
etc etc etc

..the thing i would like your opinions on is..

scenario:
i would like to split the information into:

basic info (employee ID, first name, middle initial, last name)
personal info(...)
contact info(...)
employment info(...)
and so on...

of course, all tables can be linked through the employee ID..


does it affect the application's performance, having several tables just for an employee's information? of course, sometimes all the info will be needed, so all tables will be accessed, but there are also times that only one table at a time will be accessed... i'm just not used to creating my employee table in this manner, but i was asked to do it that way.. so i'm here asking for your opinions..

thanks!