Re: Disk striping and tablespaces

>
>We are installing an HP system with multiple disk drives an multiple scsi
>controllers. We plan to stripe the file systems/raw devices across disk
>
>Given that all file systems/raw devices will be striped across disks and
>controllers is there any PERFORMANCE reason to worry about which file
>system/raw device the tablespaces, rollback segments, etc. are on or which
>tablespace a table or index is in?
I think you still need to be concerned about how you partition the database. Just because files are physically striped across multiple disks doesn't mean no bottlenecks will result if you don't plan to balance disk activity -- striping simply means the bottleneck will be a set of disks, rather than a single disk. The main advantage of striping, as far as I know, for a databse is that it allows you to create very large dataspace files without overloading the I/O bandwidth of a single device. But you still want to separate data from indexes, and spread the frequently-updated database objects across your devices.

-- 
   Vince Ventrone
   The MITRE Corporation       "...In my opinion, there's nothing
   Bedford, MA 01730           in this world beats a '52 Vincent
   vav_at_mitre.org               and a redheaded girl."  -- Richard Thompson