Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: To De-Normalize or Normalize ?

Re: To De-Normalize or Normalize ?

From: <ebohn_at_apci.net>
Date: 1998/09/25
Message-ID: <6ufigc$c02$1@nnrp1.dejanews.com>#1/1

In article <360a208f.11106841_at_news.tele.dk>,   cr_at_post.dk (Christian Roig) wrote:
> How do you get faster response-times from queries ?
>
> Some people argue that you
>
> A)
> have to De-Normalize your database, so that you have fewer joins, which in
 turn
> results in faster response-times from your queries.
>
> B)
> have to Normalize your database, so that you can have more data in memory,
 which
> in turn results in faster response-times from your queries.
>
> What is YOUR experience ?
>
> Why and/or When do YOU either De-Normalize or Normalize your database ?
>
> TIA - Christian
>
> *-*-* Disclaimer *-*-*
> The Questions, Answers, Opinions etc. stated in this
> message are my own !
>

You should always start with a normalized database design. Denormalization should only be considered if the performance is found to be lacking for your application. This is because performance is but one of serveral things a DBA is responsible for ensuring. Data quality and database maintainability are also important, especially in a distributed environment. Generally speaking, normalized databases are less prone to errors and are easier to maintain.

Generally speaking, denormalization often improves query performance at the expense of write performance. However, denormalization options for performance improvements really should be evaluated on a case by case basis.

Eric Bohn

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum Received on Fri Sep 25 1998 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US