From the course: Relational Databases Essential Training
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
When not to normalize
From the course: Relational Databases Essential Training
When not to normalize
- [Narrator] The process of normalizing a database is a good exercise to move through in order to alleviate many problems that can make a database inefficient and inflexible, but they are only guidelines. In certain circumstances, a tables design can deliberately violate one of the first three normal forms if the database designer has a good reason to do so. This is a process called Denormalization. The normalization process is all about removing redundant information from your database, and can help prevent data anomalies that can creep in when repeated information isn't updated simultaneously. Denormalization deliberately introduces redundancy in order to increase performance. Denormalization should be approached with caution, and you need to be very specific as to your reason for not having your tables neat, third normal form, and it should only be considered as an option when indexing and other performance enhancement…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.