Re: separate data/inidex

I think the problem you've particularly highlighted here, Daniel, is the massive inertia that keeps manuals (and users, and 'experts') permanently wrong.

It looks as if the two extracts are the matching entries from the 8.1.7 and 9.0.1 manuals - and the 9.0.1 manual has FINALLY corrected an error that has been reproduced faithfully from the 6.0.27 manuals onwards.

Of course, it could always go further and suggest better ways of using disks to spread the I/O load evenly - but at least it has dropped the traditional error of indexes/tables in favour of a more 'neutral' comment about 'contending data files'. Unfortunately, few of us have the time to reread all 20,000 pages of the manuals on each new release to find the odd little paragraphs which are adjustments to previous errors - so the errors keep getting quoted.

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Author of:
Practical Oracle 8i: Building Efficient Databases

Next Seminar - Australia - July/August
http://www.jlcomp.demon.co.uk/seminar.html

Host to The Co-Operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html



Daniel Morgan wrote in message <3CC4351E.244AADC3_at_exesolutions.com>...


>This is repeated in many places but here are the first two links to it I

found.


>---------------------------------------------------------------------------

------


>Place Datafiles Appropriately

>

>Tablespace location is determined by the physical location of the datafiles

that


>constitute that tablespace. Use the hardware resources of your computer

appropriately.


>

>For example, if several disk drives are available to store the database, it

might be


>helpful to store table data in a tablespace on one disk drive, and index

data in a


>tablespace on another disk drive. This way, when users query table

information, both


>disk drives can work simultaneously, retrieving table and index data at the

same time.


>

>http://technet.oracle.com/doc/server.815/a67772/dfiles.htm#423

>---------------------------------------------------------------------

>Place Datafiles Appropriately

>

>Tablespace location is determined by the physical location of the datafiles

that


>constitute that tablespace. Use the hardware resources of your computer

appropriately.


>

>For example, if several disk drives are available to store the database,

consider


>placing potentially contending datafiles on separate disks.This way, when

users query


>information, both disk drives can work simultaneously, retrieving data at

the same


>time.

>

>http://otn.oracle.com/docs/products/oracle9i/doc_library/901_doc/server.901

/a90117/dfiles.htm#7384


>

>---------------------------------------------------------------------

>