I knew this topic had come up somewhere recently, but couldn't remember where. I thought we'd tested truncate at the same time, and got the same result for both -- we're back to the Rumsfeld unknown knowns. As a thought to Waleed on why they act differently - either it's an oversight, or the whole truncate section of code is written too differently to allow the change to be inserted easily. Regards Jonathan Lewis http://www.jlcomp.demon.co.uk http://www.jlcomp.demon.co.uk/faq/ind_faq.html The Co-operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/seminar.html Optimising Oracle Seminar - schedule updated May 1st ----- Original Message ----- From: "Connor McDonald" <hamcdc@xxxxxxxxxxx> To: <oracle-l@xxxxxxxxxxxxx> Sent: Friday, May 07, 2004 4:49 AM Subject: Re: truncate a table with many extents I think that's a recent addition though. I remeber an OakTable discussion about this when we were testing 'drop' on lmt's in 8 and 9.0, the tsq$ update occurred for every extent dropped, and this was enhanced in 9.2 to be just once at the end of the drop Cheers Connor ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------