Developing a Conceptual Model › Normalizing Your Data Model › Performance

Performance

Since your data model's entities and attributes become files and fields in the database, the way you design your model affects the number of times your application system needs to access information to carry out a business transaction.

A fully normalized database breaks the data down into more files than a partially normalized one does. It, therefore, requires more input/output activities to access several files during processing.

For performance reasons, you may consider violating 3NF. You may define files that are frequently accessed as 2NF, such as files with highly volatile records, inventory records, and work records. The 2NF files contain a level of redundancy.