Using an entity model to drive physical database design

Logical relational database design, because of its implementation-independent nature, has been successfully formalized. Physical relational database design, because of its implementation-dependent nature, has remained largely unformalized and disconnected, not only from logical design but also from conceptual database design. The paper suggests a model for the physical design process that has proven useful in a number of practical development projects. The model demonstrates that a seamless join between conceptual, logical and physical design work is feasible. It illustrates how the process of annotating a conceptual model with physical detail provides a useful framework for driving the process of physical relational database design.