How to best normalize a personnel database, table options given
<p>I have an application in which I register a user using only their email and password. Then later on, they fill in their profile, which includes their personal information such as numbers, address, the hours they work during the week, etc. </p>

<p>I'm confused now whether to store all that data in the same table or to have the following:</p>

<p><code>users</code> (for authentication), <code>persons</code> (for the profile), <code>address</code> (for um, addresses), <code>numbers</code> (you get the gist). </p>

<p>I would like to know a DBA's input on this. How would you design this database for a userbase of 500 people, give or take. Are there going to be problems in the long run if I keep all the fields - around 30 right now - in the same table?</p>