title: Should a large database table be split where it doesn't improve normalisation?
body: <p>I am currently building a database system for a company that stores a lot of information about their employees. Performance isn't a massive issue as there won't be a huge amount of employees in the database (>1000)</p>
  
  <p>The database design that I have come up with so far has been normalized to an extent so employee data has been split in to separate tables where multiple data items need to stored for each employee, but there are a lot of fields which are primary key dependant so this has resulted in the main employee information table having around 50 columns. </p>
  
  <p>Is this too many and should I try to group similar items into their own table e.g a table for contact information, a table for personal information, or is it better to leave it as is?</p>