Alas, even that isn't necessarily true. What if you have a low update rate, but a high read rate. You've just isolated a disc, or two, for a very low level of redo I/O, and reduced the number of devices which are subject to the heavy I/O load. Sometimes the penalty on redo is less important than the benefit on reads. Regards Jonathan Lewis http://www.jlcomp.demon.co.uk The Co-operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/faq/ind_faq.html April 2004 Iceland http://www.index.is/oracleday.php June 2004 UK - Optimising Oracle Seminar July 2004 USA West Coast, Optimising Oracle Seminar August 2004 Charlotte NC, Optimising Oracle Seminar September 2004 USA East Coast, Optimising Oracle Seminar September2004 UK - Optimising Oracle Seminar ----- Original Message ----- From: <Paula_Stankus@xxxxxxxxxxxxxxx> To: <oracle-l@xxxxxxxxxxxxx> Sent: Friday, April 23, 2004 7:40 PM Subject: RE: Why "Separating Data and Indexes improves performance" is a myth? So in laying out disks for a new database - perhaps the only thing worth = separate out is the redo based on I/O contention - right? =20 ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------