Re: help: query tuning

Help? I'll tell you how you can help your code. Put an index on at least table_b!
Why can't you create an index? Beg to have an index put on it.

The only slightly faster way to delete your rows is to create some pl/sql and cursors to loop through one of your tables and to check against the other. If it exists, delete the row and commit inside the loop (to stop rollback segments going bananas).

Mark

ewong74_at_netscape.net wrote in message <7m60pg$o6a$1_at_nnrp1.deja.com>...
>Hi,
>
>I have the following query which take me 2 hour to finish:
>
>delete from table_a a where term_id in
>(select term_id from table_b b where a.code = b.code);
>
>table_a has 300k rows, table_b has 100k rows.
>Both tables have no indexes and i cannot create any indexes on them.
>When I do an explain plan, it looks like oracle are doing full table
>scan for both tables.
>
>Please help. Thanx.
>
>Ed
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.
Received on Mon Jul 12 1999 - 09:24:28 CDT