My user table has over 26 columns, is that normal? The db is already normalized to the 3rd level when this user table caught my eye. Is having 26 columns ok or is there some other optimization technique you use when designing your db that I should be doing?
More: What’s meant by Partitioning your table?
there’s nothing wrong with 26 columns but if they are rarely used then its different.
instead of using 26 columns, you take the one that you use less and group them using a serialize string.
change the field to a text field and then in your code you can de-serialize them and use them. if you need to update, you update the array (from your code) and then serialize it and save it to the database.