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

Home -> Community -> Usenet -> c.d.o.server -> Is this bad database design

Is this bad database design

From: pcmodeler <mark.fergel_at_bankofamerica.com>
Date: 7 Oct 2004 06:12:23 -0700
Message-ID: <3e2d808a.0410070512.20ed7cc6@posting.google.com>


The organization I work for is currently implimenting an Oracle based product from a 3rd party vendor (it tracks training history). In addition to the standard tables (associate information, etc.), there are two tables that store a lot of unlike information (employee status, country, delivery type, etc.).

Essentially, in order to get employee status, I have to link from the associate table to the lookup table to the lookup table_string table in order to get their status. Then, in order to get their country, I have to link from the associate table to the lookup1 table (a copy/alias) to the lookup_string1 table (a copy/alias). Then, to get delivery type, I have to link from the associate table to the lookup2 table (another copy/alias) to the lookup_string table (another copy/alias). This can happen up to 4 or more times. It would seem to me that this would cause some horrible performance problem in that they are throwing so much unlike information into these tables. Received on Thu Oct 07 2004 - 08:12:23 CDT

Original text of this message

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