There is a table, how much 400 columns, want to ask that can affect the efficiency?

CodePudding user response:

More than 400 columns? Data redundancy?

CodePudding user response:

Little, because want to save the data every day, every day is a list of
In order to facilitate the query

CodePudding user response:

Look at your business needs,
If can be divided into primary information and secondary information (no need to frequently access), or Suggestions for the separate,

CodePudding user response:

If you feel convenient query, performance is better, according to your method is feasible,
Generally speaking, line than column operation of the system performance is much smaller,

CodePudding user response:

The query efficiency is to look at the indexing and query the number of columns, and column number of the specific table has less to do
Update is also see index, according to the index can quickly positioning line to a specific line,
But you this design is a bit strange, every day a new column, write the efficiency is low

CodePudding user response:

Thank you
I also suggest that table, but he has been, with many columns and now do not have what problem

CodePudding user response:

You a list of one day, when the time comes a maximum of more than the number of columns to do, as if 1024

CodePudding user response:

"Every day is a list of"??
2 years more than 700 columns? Take a long-term view feasible?

CodePudding user response:

Every day there is one business day is treated as rows can be better?