Single Code Table or Separate Code tables dilemma

From: Mandar Ghosalkar <MandarG_at_gsr-inc.com>
Date: Wed, 21 Mar 2001 16:34:18 -0800
Message-ID: <F001.002D4323.20010321163530@fatcity.com>

Guys,

We r working on a Datawarehouse solution.

Our Duhvelopers want to merge all code tables into a single table by adding a codetype column.

with reference to this, i came across this article from Steve's site http://www.ixora.com.au/tips/design/meta-data.htm

i want to put them into different individual code tables instead of a single table, for the foll reasons.

1. specific attributes for a particular code type is logically and physically seperated from other code types.
2. a table lock affects only the concerned code table
3. granular control over the individual code table

i am short of arguments

wld be grateful, if ull can advise me which would be better from performance perspective.

-Mandar
--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: Mandar Ghosalkar
  INET: MandarG_at_gsr-inc.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists


--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message

to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Wed Mar 21 2001 - 18:34:18 CST