• Subject: Re: Record Length
  • From: "R. Bruce Hoffman, Jr" <rbruceh@xxxxxxx>
  • Date: Sun, 24 Oct 1999 12:46:00 -0400

-----Original Message-----
From: PaulMmn <PaulMmn@ix.netcom.com>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Sunday, October 24, 1999 4:47 AM
Subject: Re: Record Length


>As much as I like a nice, normalized database, there have been times where
>un-normalizing a database is the most effective solution.
>
>Of course, I can't think of a good example right now.


 Data warehousing or marts or files used for query purposes, such as summary
tables.


>
>However, I do insist that the database MUST be normalized to at least 3rd
>normal form at some point in the development process.
>
>The discipline of normalizing the data is the important part.  You need to
>split the data into its optimum records before you can un-normalize it.
>


Agreed. Designing to at least 3rd normal has always been the goal. And,
again, for the purposes of performance, backing off to 2nd is sometimes
(still) recommended by some.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified AS/400 Professional System Administrator
 -- IBM Certified AS/400 Professional Network Administrator

"The sum of all human knowledge is a fixed constant.
    It's the population that keeps growing!"



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.