eWEEK content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More.
2The Most Common Database Design Mistakes – Plan? What Plan?
3The Most Common Database Design Mistakes – Whats My Name?
The failure to adopt a naming standard was also cited as a problem, with each developer putting his or her own meaning on column names. Naming standards are a simple solution, with each table name and column name having a common meaning. For example, use column names that end with _date for date columns and _code for coded value columns.
4The Most Common Database Design Mistakes – Too Much, Too Little, Too Late
Experts say that developers often use too many or too few indexes, both of which are bad for performance. The trick is to measure your performance: A simple query analysis often can tell you what you need to know to decide how many indexes are needed; other times, you may have to examine the overall server performance and how it’s affected by the locking of specific indexes under load.
5The Most Common Database Design Mistakes – Everybody Needs a Friend
6The Most Common Database Design Mistakes – Tooling Around
7The Most Common Database Design Mistakes – Just What Is Normal?
8The Most Common Database Design Mistakes – This Is a RAID
9The Most Common Database Design Mistakes – Lets Get Physical
10The Most Common Database Design Mistakes – See More Slideshows Like This One
