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 -> Re: Index compression vs. table compression

Re: Index compression vs. table compression

From: DA Morgan <damorgan_at_x.washington.edu>
Date: Tue, 25 Jan 2005 14:02:08 -0800
Message-ID: <1106690375.355087@yasure>


Joel Garry wrote:

> DA Morgan wrote:
> 

>>Noons wrote:
>>
>>
>>>>So to me, there really is no such
>>>>thing as a small lookup table anymore, I rarely see anything like
>>>>Daniel's example (even a "parameter" table I'm looking at has
>>>>thousands of rows).
>>>
>>>Exactly. My experience as well.
>>
>>Help me out here ... which part of my example doesn't?
>>
>>US Zip Code table contains 42,456 rows. A Canadian postal code
>>table around 750,000 rows. But usages of the table are based
>>on the primary key and those that are not almost always use
>>an index.
>>
>>What did I miss if anything?
> 
> 
> The application that allows you to use both in the same referential
> integrity.
> 
> jg
> --
> @home.com is bogus.
> FBI agents would abuse the tools at their discretion?  Horrors!
> http://www.signonsandiego.com/uniontrib/20050125/news_1b25elgindy.html

IF / ELSE / END IF; But a very bad design: One table named postal codes will suffice.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)
Received on Tue Jan 25 2005 - 16:02:08 CST

Original text of this message

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