Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Physical Database Design - Code Tables
Paula,
I'm going to make some assumptions here, so feel free to correct me. I believe by "codetable" your referring to a one-size-fits-all lookup table for codes. Something like 1 = 'Hello", 2 = "Goodbye", etc... These typically don't become contention problems because everyone is reading from it and one or a very small number of users are writing to it and there are usually never any updates or deletes. They also are normally a lot smaller in both dimensions than the other tables being used. The easiest way to prevent this from becoming a problem is 1) index organize the table, so try to keep it as small as possible width wise. 2) Put it in the keep_pool so that it becomes memory resident.
Dick Goulet, Senior Oracle DBA
45 Bartlett St Marlborough, Ma 01752, USA Tel.: 508.573.1978 |Fax: 508.229.2019 | Cell:508.742.5795
RGoulet_at_kanbay.com
: POWERING TRANSFORMATION
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Paula Stankus
Sent: Tuesday, November 21, 2006 1:43 PM
To: oracle-l_at_freelists.org
Subject: Physical Database Design - Code Tables
Guys,
I know that for developers having the generic, one-size-fits-all codetable is easier for them to code. However, I am very worried that having one generic codetable for all applications, all tables and all code fields could cause serious contention.
Am on off here and if not, what is the best way to find out about contention.
Thanks,
Paula
Sponsored Link
Get an Online or Campus degree - Associate's, Bachelor's, or Master's
-in less than one year.
<http://o1.qnsr.com/cgi/r?;n=203;c=232538;s=2014;x=7936;f=20061101140419
0;u=j;z=TIMESTAMP;>
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Nov 21 2006 - 13:17:54 CST![]()
![]() |
![]() |