Re: Rookie asks about "Normalization"

From: <dmoyer_at_gpu.com>
Date: 1995/12/05
Message-ID: <4a1frj$rdd_at_nn2.fast.net>#1/1


In <sk952-0512950549410001_at_dffl5-10.gate.net>, sk952_at_gate.net (sam kern) writes:

In a completely normalized database design, most likely performance will suffer due to the many joins that would have to be done to get all pertinent data. The rule of thumb that we use is normalize until it works then de-normalize until it hurts.

scott moyer
dmoyer_at_gpu.com

>I have been working on a Computerized Maintenance Management Application that
>has been developed by the RJN Group From Chicago.
>Our Newly Formed MIS Division is pushing to scrap this application for one
>of their own design, with their major complant being that the plant
>program is not
>"normalized".
>Could anyone explain this concept,RJN says that a completely normalized app.
>would be Ideal but is not always the best; I would appreciate any
>info!
>Thanks Ahead of Time
>Sam
Received on Tue Dec 05 1995 - 00:00:00 CET

Original text of this message