Re: DB Design Principles for RDBMS
From: stu <smcgouga_at_nospam.co.uk>
Date: Fri, 7 Mar 2003 08:48:56 -0000
Message-ID: <b49mgq$gae$1$8300dec7_at_news.demon.co.uk>
Date: Fri, 7 Mar 2003 08:48:56 -0000
Message-ID: <b49mgq$gae$1$8300dec7_at_news.demon.co.uk>
"Tony" <andrewst_at_onetel.net.uk> wrote in message
news: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!"
I read somewhere that it is a good idea to start with a fully normalised db then selectively denormalise only when you have a good reason to do so.
Stu Received on Fri Mar 07 2003 - 09:48:56 CET