Why many designs ignore normalization in RDBMS?

Posted by Yosi on Programmers See other posts from Programmers or by Yosi
Published on 2013-09-28T22:16:04Z Indexed on 2013/10/26 22:14 UTC
Read the original article Hit count: 267

I got to see many designs that normalization wasn't the first consideration in decision making phase.

In many cases those designs included more than 30 columns, and the main approach was "to put everything in the same place"

According to what I remember normalization is one of the first, most important things, so why is it dropped so easily sometimes?

Edit:

Is it true that good architects and experts choose a denormalized design while non-experienced developers choose the opposite? What are the arguments against starting your design with normalization in mind?

© Programmers or respective owner

Related posts about design

Related posts about sql