The Mother of All Database Normalization Debates

Over at “Coding Horror” blog, Jeff Atwood published an interesting article titled “Maybe Normalizing Isn’t Normal“.

But more than the article itself, the debate that ensued in the comments there is very interesting. The “High Scalability” blog published a compilation of some of the interesting quotes from the debate. This compilation provides a great overview of the (admittedly long) discussion.

I would recommend that you read the original article first and then the compilation of the quotes at the High Scalability blog.

This entry was posted in Databases and tagged , , . Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

8 Comments

  1. Posted October 28, 2008 at 2:04 pm | Permalink

    Normalization is a double sided sword. You need to know when to stop normalizing.

    I had a case where I had to join the same table again and again ( table joined with the same table) to get few rows of data. The app performance was pathetic just because of complex queries. (due to highly normalized tables)

  2. sappani
    Posted December 23, 2008 at 6:09 am | Permalink

    yenna mame, sappunu oru matter ah solli irukka….

  3. Posted December 30, 2008 at 4:40 am | Permalink

    You can do both!

    Normalize the Master or Origin information and De-Normalize of the deployment of the information that is used for look-ups.

    We do this all of the time and real life. The information we USE is a De-Normalized version of the database for most re-life uses. For example out day-timer. The internal version may be very folded or normalized.

    The bank creates a De-normalized version of information on paper as a backup for bank use if the database is down and as a cross reference.

    Do the same for your applications. For example, once a day compile the “stats” that the user sees on the web page from the Normalized internal schema. Let the user know that this is a “once a day” roll up of the stats. Now the action needed for this web page will be VERY fast. The over head low. You have a fast solution. The information is NOT real time, but the user gets a quick reply.

    Edward M. Goldberg
    http://Blog.EdwardMGoldberg.com

  4. Nathan
    Posted June 4, 2009 at 12:16 pm | Permalink

    Normalization is nothing just read the following link

    http://sqldbsolution.blogspot.com/2009/06/normalization-is-first-step-for-db.html

    By nathan

  5. Posted August 30, 2013 at 7:15 pm | Permalink

    If you wish for to obtain much from this paragraph then you have to apply such methods to your
    won webpage.

  6. Posted December 14, 2013 at 10:29 pm | Permalink

    You realize as a result significantly regarding this issue, forced me to be on their own imagine them at a number of different aspects. The for instance women and men aren’t engaged except it can be think about attain together with Rhianna! Your stuffs superb. Constantly keep it upwards!

  7. Posted December 17, 2013 at 4:51 am | Permalink

    Someone specifically help to create severely content I’d state. Option first-time My partner and i been to your web web page and so considerably? I amazed while using the exploration you have made to develop this actual post outstanding. Excellent job!

  8. Posted January 9, 2014 at 3:47 am | Permalink

    Hello, all is going sound here and ofcourse every one is sharing information, that’s
    really excellent, keep up writing.yoga exercises to
    Reduce high blood pressure

  • About grok.in

    This is a blog primarily focussed on the subjects of Information Engineering—Retrieval, Extraction & Management, Machine Learning, Scalability and Cloud Computing.