From the course: Learning Relational Databases
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Denormalization
- [Instructor] We've just gone through and normalized our database design by running through the requirements of the normal forms. Here and there though, there might be a reason to undo some of those changes. Or keep our database design in a format that doesn't strictly adhere to the requirements of a particular normal form. This is a process called denormalization. Denormalization should be approached with caution and you need to be very specific as to your reasoning for not having your tables meet the third normal form. The normalization process is all about removing redundant information from your database and helping to prevent data anomalies that can creep in when repeated information isn't updated simultaneously. So why would you want to denormalize a table? Two reasons: performance and to track historical data. First, let's take a look at performance. You might have noticed that the common solution for all of our normalization procedures was to create an additional related…
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.