Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a user profile table that has 32 fields. These fields are always updated and accessed at the same time. I’m wondering what’s the better design, this 32 field-table or split the table into smaller tables and join through a view? Or even, it’s possible that the best is split the big table and join it through a SELECT … JOIN
If the data is not hierarchial, it is of no use to split the table. Instead it will result an extra overhead while executing the joins. On the other hand if you have repetitions of records in this table, go ahead for a split. It will preform better.