Greetings, I suspect this may date back to the "old days." I remember some years ago a statement, I believe it was in an Oracle Press book on oracle administration, that the ideal number of disks for a database was 28 (maybe not that many but close). This was in days when disks were smaller and performed differently. The idea was to spread things out across several disks, data, indexes, online redo logs, archive logs, undo, temp space, etc. so that I/O bottlenecks would be minimized. With today's faster and bigger (huger actually) disks this is not only less of an issue but difficult to do. How can you do that on a machine with 1 500GB disk? Why? Thanks. Bill Wagman Univ. of California at Davis IET Campus Data Center wjwagman@xxxxxxxxxxx (530) 754-6208 From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Bobak, Mark Sent: Thursday, May 15, 2008 11:27 AM To: ricks12345@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx Subject: RE: concepts document part about separating indexes and tablspaces If it says that, someone should file a documentation bug to get it fixed. -Mark -- Mark J. Bobak Senior Database Administrator, System & Product Technologies ProQuest 789 E. Eisenhower, Parkway, P.O. Box 1346 Ann Arbor MI 48106-1346 +1.734.997.4059 or +1.800.521.0600 x 4059 mark.bobak@xxxxxxxxxxxx <mailto:mark.bobak@xxxxxxxxxxxxxxx> www.proquest.com <http://www.proquest.com> www.csa.com <http://www.csa.com> ProQuest...Start here. From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Rick Ricky Sent: Thursday, May 15, 2008 2:17 PM To: oracle-l@xxxxxxxxxxxxx Subject: concepts document part about separating indexes and tablspaces i was talking to someone about this today. I cannot remember where in the Concepts document that it says that separating data from indexes improves performances?