Re: optimizing in delete-statement

Ralf Beutler wrote:

> DA Morgan wrote:
>
> > My guess is that you have multiple things wrong. Start with an EXPLAIN PLAN.
> > .. post the plans.
>
> DELETE STATEMENT ()
> DELETE () TROUTE
> NESTED LOOPS ()
> VIEW () VW_NSO_1
> SORT (UNIQUE)
> TABLE ACCESS (BY INDEX RO TUSERXORGANIZER
> INDEX (RANGE SCAN) I_TUSERXORG_FKUSERID
> INDEX (UNIQUE SCAN) SYS_C001926
>
> I can't see something wrong.
>
> br | rb
> --
> Sie freuten sich riesig, wenn eine Maschine nach sechs Stunden etwas
> fertig brachte, wozu jeder Mensch auf der Straße für 2 Cent fähig
> gewesen wäre. Anschließend ließen sie sich Bananen- und Sushi-Pizza
> kommen und schliefen vor der Tastatur ein. [aus T.P., Heiße Hüpfer]

This is taking 30 seconds on 58,000 rows? Hmmm.

Is it 58,000 rows in the table or 58,000 rows that are being deleted? What is the breakdown between total rows and deleted rows?

Please don't snip as it is hard to remember specific posts when I can't see them.

Daniel Morgan Received on Tue Feb 11 2003 - 10:50:40 CST