Re: Dropping Tables - Slow Performance

From: Ronald <ronr_at_wxs.nl>
Date: Thu, 4 Feb 1999 21:28:57 +0100
Message-ID: <01HW.B2DFC19900058052127BBD30@news.wxs.nl>

On Wed, 3 Feb 1999 21:56:02 +0100, Rodgers, Tony (CEI-Atlanta) wrote (in message <529B47EE34C4D1118D0800A0C99ABC983288FA_at_EATL0S04>):

> 
> Normally, I would agree with you, but  while TRUNCATE+DROP "Should" be no 
> faster than just DROP, I have first-hand experience from 7.3.2 in data 
> warehouses that TRUNCATE+DROP indeed was *considerably* faster than just 
> DROP.   As for the theory of dirty blocks being written out, I don't think 

snip
>> My personal opinion is that TRUNCATE + DROP should be no faster than a
>> simple DROP, however, just for the sake of argument ...
>>

> 	[Rodgers, Tony (Atlanta)]  Snip 

>>
>> What if a TRUNCATE as it drops the high water mark somehow tags the blocks
>> in the db_block_buffer as empty so that they do not have to be written,
>> but can be discard like temporary blocks ?
>>

> 	[Rodgers, Tony (Atlanta)]  Snip . 
> 

>> Jonathan Lewis Yet another Oracle-related web site: www.jlcomp.demon.co.uk
>>
>>

> [Rodgers, Tony (Atlanta)] Snip
>

How about first revoking the privileges on the objects to drop ? --

Ronald  -  Unix SA               http://home.wxs.nl/~ronr/professional.html

        -  Oracle DBA            http://www.tresco.nl  
        -  Middleware programmer/
                      designer   mailto:R.Rood_at_tresco.nl
 

Received on Thu Feb 04 1999 - 14:28:57 CST