posted 17 years ago
Assuming you are storing data in a relational database then the concept of normalisation must come in to play here ...
if storing all person data in one table will mean there will be redundant data then this should be avoided.
classic example is Employees and Departments;
an Employee may work in only one Department
but a Department may employ many Employees
so we make one table for Employees and one table for Departments - otherwise for employees working in the same department we will end up storing the department name many times (redundant data).
more difficult to maintain data integrity in this case - when the dept name changes need to find all occurences of the dept name - dept name may end up coded slightly differently for different emps (IT, I.T, it, ...).
Depends on your data - if data in the tables is related in a one-to-one relationship then could store in one table.
Hope this helps.