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.


>Hello,
>
>I create a software for managing tax information. There is a personal info and the financial info that needs to be stored, and my question is whether it is a good practice to make one table with all the fields (personal information and financial information) or to make two tables, one for the personal information and another for the financial data with a one-to-one relationship.
>I'm interested whether there are any rules according to data-normalization or good practices.
>
>Thanks for your time in advance!