How to properly organize the structure of a table in a database?

Question

MySQL

Hey!
Such situation. There is a certain CRM, and there is an entity "client". The application is constantly expanding, and now the table has more than 40 fields. So I think what to do if it expands further. Add new fields as well, or it's better to split the fields into separate tables. How is it generally recommended to do this, how it will affect the performance of the database with data growth, and in general I would be grateful if you give literature on this topic, about database design, which describes such moments. Thanks...

Answer 1

it usually only makes sense to divide into tables with a one-to-one relationship only to put "heavy fields" or fields with information on which there will usually not be a sample into a separate table.
if the table is constantly expanding, and you don’t want to constantly expand the database, you can make an xml-type field with xml in which you can simply add fields as needed, and when you get used to transfer them all at once to the table itself
, in general, read, understand