There are about 56 fields for the financial and 40 fields for the persons data.
Doesn't data normalization require one table if two tables would have a one to one relationship? I heard that you should make child tables only if there is a one to many relationship present.
Which practical advantage would it make to make child tables with a one to one relationship?

>I think the "right" answer will depend on your particular application.
>
>Out of the blue, separating the data in two tables to represent their different nature (personal/financial) makes sense to me.
>
>How many fields are used for personal and how many for financial information? Let's say that only one or two fields are used for financial data, then splitting the data probably won't be worth the hassle. On the other side, if there are 20 fields specific for financial data, then the split will probably be a good idea.
>