normalization and good table design
We all will agree that a good database design is the key for performance and easy front end application development. If your data is not normalized and distributed among tables properly the performance will suffer with high chances of bad data.
Signs of good table design
- Table should not be over normalized, too many joins will slow down the query and front end application will become more complicated.
- Table should have primary key a unique identifier for each row.
- If table is referenced to another table then create foreign key constraints. Avoid controlling data integrity on front end only.
- Each table should contain data only for one business entity.
- You should avoid NULL columns during design, try using default values if possible.
- A table should not have unnecessary columns.
- If calculation is required and your database engine supports computed columns, then use computed columns.
- Avoid too many indexes on table.