Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Does the order, arrangement or grouping of columns with large (such as long text descriptions) and small (such as bit and tinyint) field types have any noticeable impact on MySQL (InnoDB engine) querying performance when table sizes get large and JOINs need to be done on them? E.g. should I put all of the bit/tinyint fields first?

What about most common queries? Could querying be faster if one were to front load the table with what might be the most commonly used columns?

Based on this (and/or other considerations), should I plan my table structure based on the field type, or is something like an alphabetical order just as good?

share|improve this question

closed as primarily opinion-based by Max Vernon, Phil, mustaccio, Shanky, dezso Nov 5 '15 at 13:09

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.