Re: DB Design Principles for RDBMS

From: Tony <andrewst_at_onetel.net.uk>
Date: 6 Mar 2003 09:54:58 -0800
Message-ID: <c0e3f26e.0303060549.1cd5c72c_at_posting.google.com>

Anton Versteeg <anton_versteeg_at_nnll.iibbmm.com> wrote in message news:<3E477A6C.B4CD774C_at_nnll.iibbmm.com>...
> 4. Do not over-normalize your database design

I'm not sure how useful that advice is to someone new to database design. They may think: "Hmmm... having to join from order_line to order to get the customer name is a bit much - let's not take normalisation THAT far!"

It seems to me that proper normalisation is NOT "over-normalisation", and it is far more common to see under-normalised database designs than over-normalised. Received on Thu Mar 06 2003 - 18:54:58 CET

This message: [ Message body ]
Next message: OlegJay: "Logically model never possible real world or my forever imperfect business?"
Previous message: Pablo Sanchez: "Re: many to many relationship"
Next in thread: stu: "Re: DB Design Principles for RDBMS"
Reply: stu: "Re: DB Design Principles for RDBMS"
Maybe reply: RayD: "Re: DB Design Principles for RDBMS"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message