Re: separate data/inidex

I hate "me too" posts, but this is about the best summary I've every seen of the real issues involved in a RAID-less set up, and it's what I would have posted if I'd been less tied up with other things.

Best Regards
HJR [Snip]

> If you want a simple starting approach for unexceptional
> database systems, and you absolutely cannot stripe
> your filesystems :-
>
> Reserve drives for redo
> Reserve drives for archived redo
> Create one rollback tablespace per device
> Create a couple of files per drive for a TEMP tablespace
> Allow about two to four tablespaces per drive for tables
> Allow about two to four tablespaces per drive of indexes
> (The separation of indexes and tables is for admin
> NOT performance reasons)
> Allocate segments to tablespaces in a way that you feel
> will balance physical I/O, and map objects of about the
> same size to the same tablespace.
> Start looking for special cases, e.g. a very large table
> with highly random I/O requirements, which may need
> its own tablespace spread at one file per device.
>
> And before you do all that, try to work out when you
> are going to need to grow into some new disks and
> figure out how you can fit them into the pattern
> without rebuilding the entire database.
>
Received on Tue Apr 23 2002 - 16:21:57 CDT