Re: query tune

I don't understand this truncate solution. We all know that when this kind of reorganization has to be repeated on a regular basis, the truncate isn't a real silver bullet. One should find the root cause of the problem, and solve that. In this case, I would simply drop the table. That saves a lot of future work, and performance can not degrade again. Of course the statement will fail then, but as many teachers tought us: The best way to execute a statement is stop executing it. Problem solved.
Just my $0.02

Best regards,

Carel-Jan Engel

===
If you think education is expensive, try ignorance. (Derek Bok) ===

On Wed, 2005-03-16 at 00:38, Alexander Gorbachev wrote:

> > TRUNCATE TABLE URL_PAGES drop storage;
> Oracle is clever enough and does this optimisation by default with tuncate.
> Unfortunalte this solution is temporary and you need to schedule the
> job that truncates the table every now and again. Otherwise,
> performance will degrade again.
> If the job is scheduled often enough it could be nice to include, on
> the contrary, KEEP STORAGE clause.

--
http://www.freelists.org/webpage/oracle-l