When to split a (MySQL) table

188 Views Asked by At

I have a user table for my website and I am currently in the process of redesigning the entire thing.

The information I will store will consist of about 30 fields. Not all fields are required for all users. For example, users can have address information (street, city etc.) and bussiness information (company name, number, etc.).

I'm wondering if it would be best in this case to have a large table with 30 fields (where some fields can be null), or to split up the table into multiple tables linked by user IDs with foreign keys. What would be the pros and cons in terms of

  • Best practice (clear and organized code/database)
  • Speed
  • Storage space

I know there are similar questions about this topic but I couldn't find any that matches my case. Please let me know what you think.

0

There are 0 best solutions below