Chapter Summary
- When you design a database, you should do it as a formal process.
- For conceptual modeling, use ORM.
- ER models are standard for the logical level. ER diagrams are usually part of the application documentation.
- Check your model by using normalization.
- Denormalize for performance and history. Denormalize deliberately and thoroughly document your denormalization changes.
- Plan your data flow at design time.
- Take special care to find supertypes and subtypes during the design process; retrofitting an existing database to accommodate missed supertype and subtype relationships can be difficult.
- When talking about hierarchies, be sure to distinguish between graphs and trees and model each type appropriately.
© Microsoft. All Rights Reserved.