3 ms·
84 fields in one table is terrible DB design, and I'm not surprised that it's slow. If it were me, I'd split that one giant table into a "main" table with some
by jlarocco 13y ago
84 fields in one table is terrible DB design, and I'm not surprised that it's slow.
If it were me, I'd split that one giant table into a "main" table with some basic information and foreign keys pointing to other tables with the more detailed information from the other sources.
- webstartupper 13y agoYour assumption is that all fields are not required in the default search query. In our case, joining 6 tables with 14 fields each is going to be much slower than running the query of just the table.