Re: Documentation contradiction?

In my experience this is the difference between need to have and nice to have. For most production systems I have worked on I have strenuously argued for the maximum amount of separation of data/indexes/redo/control files as possible. In this era of 18G disks this can be a little expensive (the good ole days of 2G disks) but worth it especially in a active OLTP environment.

I have also worked on development systems that have had the whole shooting match (OS, Oracle, development env and backups!) on the single internal (mirrored mind you) spindle. It was a little slow, but got the job done.

In the end, your job is to maximize performance from the environment that you are managing. This can also include managing the system the database is hosted on as well to trying to meet performance expectations from the user/developer community. I am not trying to gloss over the technical aspects of managing I/O on the system, but that is a topic that can be far too involved for a discussion group thread. Read/Write latency, bus speed, system and controller cache all contribute to system performance and must be taken into account.

Not an easy job, but if it was anyone could do it?

SC

> Hi Folks,
>
> These excerpts from Oracle 8i documentation "appear" to be in contradiction
> to me. Seperate data and indexes on separate drives or not!. Am I correct
> or confusing apples and oranges so-to-speak.
>
> Separating Tables and Indexes
> -----------------------------
> It is not necessary to separate a frequently used table from its index.
> During the course of a transaction, the index is read first, and then the
> table is read. Because these I/Os occur sequentially, the table and index
> can be stored on the same disk without contention.
>
> from
> Oracle8i Tuning
> Release 8.1.5
> A67775-01
> 20
> Tuning I/O
>
> 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.
>
> from
> Administrator's Guide
> Release 8.1.5
> A67772-01
> 10
> Managing Datafiles
>
> Sean :)
>
> ###### ###### ###### ######
> # # # # # # # # Rookie
> #### # # ###### ###### Data
> # # # # # # # # Base
> # # ####### ###### # # Adminstrator
> -------------------------------- ------------
> Organon (Ireland) Ltd.
> E-mail: sean.oneill_at_organon.ie [subscribed: Digest Mode]
>
> The only man who never makes a mistake is the man who never does anything.
> - Theodore Roosevelt
>
> --
> Author: O'Neill, Sean
> INET: Sean.ONeill_at_organon.ie
>
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from). You may
Received on Wed Aug 09 2000 - 10:03:57 CDT