>
> If I have a large table with a column defined as "unqiue index", will
> it cause performance problem in a high inserting rate environment(all
> single insert)? I heard from someone that if the index is "unique", the
> insert will have to "lock" the top node of the index tree to update the
> index. Thus it will cause a lot of latch contention under hight
> inserting case. But I suspect this is not the case. It might be true
> for some type of databases, but I don't think Oracle does this. Can
> someone offer some insights here?
>
>
By single insert, do you mean single insert statement or single row insert?
What's the average number of rows being inserted in a transaction?
Received on Sun Aug 13 2006 - 18:59:02 CDT
