Common design mistakes
The previous modules in this course described the logical design, physical design, and, to a lesser extent, implementation stages of the DBLC. This module offers a number of insights into the overall design process by identifying common design mistakes and providing tips on how to avoid them.
After you have completed this module, you should be able to:
The next lesson lists the four areas of common design mistakes.
- List the four areas of common design mistakes
- Describe mistakes associated with business objects and business rules
- Describe mistakes associated with columns
- Describe mistakes associated with constraints and keys
- Describe mistakes associated with relationships
and referential integrity
- Describe mistakes associated with international issues
- Interpret the statement: "There are no wrong databases, just useless ones."
Items in a business environment that are related, and about which data need to be stored (e.g., customers, products, orders, etc.)
A set of rules or conditions describing the business polices that apply to the data stored on a company databases.
Part of the structure of a database table; also known as a field or, during early database design, as an attribute.
If the same attribute occurs in more than one table, a relationship exists between those two tables.
The means of maintaining the integrity of data between one or more tables that relate to each other--in other words, that a column of data in a table has a null or matching value in a corresponding table. Referential integrity is usually enforced with foreign keys.
 international issues:
Database design considerations based on other countries differing data standards, alphabets, and writing systems.