• Lynn Pettis - Wednesday, November 22, 2017 3:34 PM

    Thom A - Wednesday, November 22, 2017 3:20 PM

    Lynn Pettis - Wednesday, November 22, 2017 3:14 PM

    Hugo Kornelis - Wednesday, November 22, 2017 3:06 PM

    Lynn Pettis - Wednesday, November 22, 2017 1:37 PM

    Was I taught wrong regarding normalization?  I was taught that you normalize to a point, say 3NF, then de-normalize where appropriating knowing the trade-offs and possible issues that you would need to account for in the design.

    Correct. Well, except that you should normalize up to 5NF before you start denormalization.
    Many people in the world appear to confuse "de-normalized" with "non-normalized"

    Well, I was using 3NF as an example.  I would also think it would be dependent on the complexity of the data being modeled as well.  Not sure I would go to 5NF for a simple database system.  Thinking about it, I really think it depends on the data anomalies you encounter during the process.  If I remember correct the order of normalization is 1NF, 2NF, 3NF, BCNF, 4NF, 5NF, 6NF.  After 3NF I have a hard time remembering what data anomalies you are overcoming.  I would actually have to look those up.

    What brought on the sudden self doubt Lynn?

    Just some former MVP espousing normalization and his never wills in the same breath.

    Heh... since I'm no longer an MVP, I hope like hell that you're not talking about me! 😉

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)