Re: Database Design Best Practice help

From: mike boligan <mboligan_at_yahoo.com>
Date: Mon, 28 Jan 2013 07:02:53 -0800 (PST)
Message-ID: <1359385373.19839.YahooMailClassic_at_web164006.mail.gq1.yahoo.com>

Jose,
    You have gotten alot of good responses.  While these responses can help you through your immediate question, something that may help you longer term would be to read the book "The Art Of SQL" by Stephane Faroult.  It answers exactly this question and many others like it.  I highly recommend it.

    Also, I would like to point out, I do not know nor have I ever met Stephane.

Mike

• On Mon, 1/28/13, Jose Soares <jose.soares_at_sferacarta.com> wrote:

From: Jose Soares <jose.soares_at_sferacarta.com> Subject: Database Design Best Practice help To: oracle-l_at_freelists.org
Date: Monday, January 28, 2013, 4:03 AM

Hi all,

I have a question about database design best pratice.

In my db I have about one hundred tables like this:

code
description

To avoid to have a so great number of similar tables in the db I wonder if it is a good idea to unify all these tables in one big table like this:

id
code
table_ name
description

The advantages are:

1. only one table in the db instead of 100
2. only one controller to manage the table

Could this be a way to enhance db performance? Is there any negative point that I don't see?

Thanks for any comments.

j

--

http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Mon Jan 28 2013 - 16:02:53 CET