July 11, 2008

The basic principles of relational database design. Part 2

Filed under: Database, MySql — admin @ 12:25 pm

<< Part 1

Source: Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design by Michael J. Hernandez

Everything has a beginning, and the database design process is no different. Interestingly enough, you start the process by defining the end result.

Figure 1. Each of the tables is represented by a rectangle. The diamand represents the fact that there is a relationship between these two tables.

Guidelines for Creating a Table Names

  1. Create a unique, descriptive name that is meaningful to the entire organization. Choose names that are descriptive enough to be self-explanatory.
  2. Good Example: “Vehicle Maintenance”.

  3. Create a table name that accurately, clearly, and unambiguously identifies the subject of the table.
  4. Bad Example: “Pieces”, Good Example: “Engine Components” and “Body Components”.

  5. Use the minimum number of words necessary to convey the subject of the table.
  6. Bad Example: “TD_1″ or “Multi-Use Vehicle Equipment”, Good Example: “Equipment”.

  7. Do not use words that convey physical characteristics.
  8. Bad Example: “File”, “Table”, “Record”; Good Example: “Patient Record”.

  9. Do not use acronyms and abbreviations.
  10. Bad Example: “SC”; Good Example: “Security Codes”.

  11. Do not use proper names and other words that will unduly restrict the data that can be entered into the table.
  12. Bad Example: “Southwest Region Employees”.

  13. Do not use names that implicitly or explicitly identify more than one subject.
  14. Bad Example: “Facility/Building”.

  15. Use the plural form of the name. Table represents a collection of similar objects or events. By following this rule it’s easy to differentiate between table names and field names.
  16. Bad Example: “Home Phone”; Good Example: “Home Phones”.

>> Part 3


No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a comment