Re: Database Design Best Practice help

From: John Hurley <hurleyjohnb_at_yahoo.com>
Date: Mon, 28 Jan 2013 11:35:48 -0800 (PST)
Message-ID: <1359401748.69689.YahooMailRC_at_web181203.mail.ne1.yahoo.com>

So it looks like you have examples of a design with entities ( specie / movement / disease ) already in the model.

I have not seen probably all the responses but most already noted that changing to a generic design from a specific design is probably not a very good idea.� Current design can ( you tell me if it is used ) support referential integrity.

Original Message ---- From: Jose Soares <jose.soares_at_sferacarta.com> To: oracle-l_at_freelists.org Sent: Mon, January 28, 2013 2:02:39 PM Subject: Re: Database Design Best Practice help

These tables are simple coding tables used for selection list , here some:

movement
� code |� � � � description

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


� � 11 | Theft

� � 12 | Move out to slaughter house

� � 15 | Home slaughtering

� � 17 | Export to third countries

� � 16 | Export to EU countries

� � 1 | Birth

� � 2 | First tagging

� � 5 | Move in

� � 4 | Import from third countries

� � 8 | Move out

� � 14 | Death

� � 18 | Reidentification for lost ID

� � 7 | Move in from Temporary Export

� � 10 | Move out to� Temporary Export
� � 3 | Import

desease
� code� | description

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


� ATH� � | Antrax (Multiple Species)

� BTV� � | Blutongue (Multiple Species)

� 002� � | Rabies

� 001� � | TBC

� OVS� � | Old world screwworm/Chrysomya bezziana(Multiple Sp

� BRM� � | Brucellosis/Bucella Melitensis (Multiple Species)

� FMD� � | Foot and mouth disease (Multiple Species)

� BRU� � | Brucellosis/Brucella Abortus (Multiple Species)

� NWS� � | New world screwworm/Cochliomyia (Multiple Species)

� PTB� � | Paratubercolosis (Multiple Species)

On 01/28/2013 02:57 PM, John Hurley wrote: > I guess my first question is do you know "why you have about one hundred tables

> like this ..." in the current database?
>
> Do they represent different entities in some fashion that correspond to some
> part of the real world?
>
> Do these tables ONLY have the two columns code and description or is there all
> sorts of other columns in ( some/all ) of them?
>
> Do you have any understanding of the history of how and why the current set of
> tables were ( pick one ) created/designed/arrived in your database?
>
>
>
> ----- Original Message ----
> From: Jose Soares <jose.soares_at_sferacarta.com>
> To: oracle-l_at_freelists.org
> Sent: Mon, January 28, 2013 4:03:16 AM
> Subject: Database Design Best Practice help
>
> 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
>
>

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

Received on Mon Jan 28 2013 - 20:35:48 CET

This message: [ Message body ]
Next message: Christopher.Taylor2_at_parallon.net: "RE: oracle client"
Previous message: Jeffrey Beckstrom: "Re: oracle client"
In reply to: Jose Soares: "Re: Database Design Best Practice help"
Next in thread: mike boligan: "Re: Database Design Best Practice help"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message