Re: Delete/Insert and high number of concurrent users

Depending on what the application does with the data, it may be possible to declare the table as a global temporary table. This would give every user their own 'temp segment' copy of the table - which might help to reduce the problems of delete and read-consistency costs. If you can also arrange for the table to be

    on commit delete rows
you may also avoid any costs of a delete - because the data will have disappeared on a prior commit. If the table has to be

    on commit preserve rows
you can avoid most of the cost of the delete by truncating. (Though I have seen an odd latching and parsing effect that might have been due to excessive truncating on a GTT).

-- 
Regards

Jonathan Lewis

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 Sept 19th





"Gautrak" <gautrak_at_yahoo.com> wrote in message
news:76ceef56.0409190825.240ff9a8_at_posting.google.com...


> Hi,

> Oracle version : 9.2

>

> A transaction, in addition to other statements, involves first

> deleting all records belonging to that userid and then insert fresh

> set from another table.

> The database must be able to support large number of users, each with

> own userid, performing this transaction.

>

> I believe this is not a good design but have no control on this part.

>

> To ensure that these delete statements do not result in any

> bottlenecks, what should be the focus areas.

>

> Thanks and regards,

> Gautrak