I have looked at similar questions such as this one Does number of columns affect MYSQL speed?
I will try to ask my question with more specification as it is slightly different.
I have the option of having a table like this;
UserID | Parameter 1 | Parameter 2
The table will NOT have any relational SQL performed on it.
The queries will only read/write Parameter 1 OR Parameter 2 for a group of UserIDs.
Parameter 1 will be required more than 10 times as often as Parameter 2
Parameter 1 will store a data string of up to 1000 characters
Parameter 2 will store a data string of up to 100000 characters
I have a choice of format for these so I think TEXT(1000) or Blob for Parameter 1 and MEDIUMTEXT(100000) or MEDIUMBLOB for Parameter 2 would be valid. Note I just need to read/write these - I am not sure what the format choice would do to DB performance (minor question).
My main question is this; given the frequency of access to Parameter 1 and Parameter 2, the independence of the Parameters, and given the much greater size of Parameter 2, should I have one table;
UserID | Parameter 1 | Parameter 2
OR two tables;
UserID | Parameter 1
UserID | Parameter 2
This is an edit to make things clearer. I am interested in the performance difference of the two table options given the previous description. I am especially concerned that the inclusion of the larger and less used Parameter 2 will have a significant impact on the performance when accessing Parameter 1. You may consider that the effect if there are 1000s of rows.