Denormalization Guidelines for Base and Transaction Tables Douglas B. Bock Department of Computer Management and Information Systems Southern Illinois University Edwardsville Edwardsville, Illinois 62026 USA John F. Schrage Department of Computer Management and Information Systems Southern Illinois University Edwardsville Edwardsville, Illinois 62026 USA Abstract This article outlines heuristic guidelines for denormalizing transaction tables in relational databases. Denormalization as a process seeks to improve the response time for data retrieval while maintaining good system performance for row insertions, updates, and deletions. These guidelines apply especially for client-server environments where response time for on-line, transaction-processing systems is critical to end-user satisfaction and productivity. 1. Introduction Normalization as part of the conceptual design phase focuses on developing well-structured relations (tables). A wellstructured relation minimizes redundant data storage and supports data manipulation language processing for row insertions, deletions, and updates without introducing errors or data inconsistencies termed anomalies. While a fully normalized database schema reduces the possibility of anomalies, it can introduce other types of problems. These include inadequate system response time for data retrieval and storage, and referential integrity problems due to the decomposition of natural data objects into relational tables. A successful database administrator must trade-off the benefits of normalization
/lp/association-for-computing-machinery/denormalization-guidelines-for-base-and-transaction-tables-jztLWAQ9kk