Re: A database design question

From: Dan Townsend <townsend_at_ebmud.com>
Date: 1997/08/01
Message-ID: <33E234DC.9E3@ebmud.com>#1/1

On Wed, 30 Jul 1997 15:07:04 -0500, Sanjay Rallapally
> <c696346_at_showme.missouri.edu> wrote:

>
>Its me again,
>I am curious abut the level of database  normalization that is
>followd in the real-world . How rigidly do u guys follow the database design
>rules regarding normalization? Lastly, when is it better to have an unnormalized
>table, than an unnormalized one? I mean, how useful are indexes as against
>having a normalizzed table

I consider normalization a vital goal. In my experience, inordinately complex programming tasks later in a project are often due to improper database design earlier in the project. Since you probably won't know everything you are going to find out later, normalization provides a safety net against later traps.

Consider it like the speed limit. We all push it a little, but hopefully not enough to get arrested. Slow down and normalize better and you will feel more comfortable about the future of the project.

PS: I agree with terryg8 that normalization is about the MODEL, more than the technical definitions of third normal form. If the Model is right, normalization is a natural part of the design process. It does not guarantee success, however, as the programming also needs to be done right.

+-----------------------------------------------------
| Dan Townsend, Supervising Database Architect

| EBMUD Enterprise Object Designer
| mailto:townsend_at_ebmud.com

+-----------------------------------------------------

Received on Fri Aug 01 1997 - 00:00:00 CDT