Splitting high transaction volume table?

I have a table that is going to be hit (either a read or a write) on almost every transaction that takes place in my database. Would there be any speed/efficiency benefit to splitting the table schema into two, three or four narrower tables and relating them with a common key, or is Oracle's architecture efficient enough so that this step would not be necessary?

Thanks - Tom Received on Sat Aug 21 1999 - 15:53:02 CDT