Scav wrote:
Helpful folks,
I am trying to find any doc or research or studies comparing the pros
and cons of architecting a DB2 disk subsystem to physically segragate
index access and data access on separate spindles, as opposed to
putting both index and data on one RAID group and assuming the
striping will provide adequate segregation.
Can anyone point me in a good direction for finding such info?
Thanks in advance
Sean
You need to start with the performance guides and build your
understanding of the pro's and con's of each storage mechanism. Once you
have this understanding, you'll need to apply it to your expected load
and then verify it against the actual load placed on the disk subsystem.
Separate disks isolate physical arm movement of data and indexes. Raid
cannot do this because the array is (usually) treated as a single disk.
The simplest isolation; a separate single drive for indexes and data
will allow twice the number of arm movements per second than placing
both components of the data base on a single drive.
Raid-5 type arrays need to be examined very very carefully. The normal
write procedure for this mechanism requires reading data from all of the
disks in the array and always writing data to a minimum of two disks.
When the database manager is in a "wait for write operation to complete"
state, the potential delays for the multiple reads and writes can be
significant. Hardware is available for raid arrays that may alleviate
this problem.
Phil Sherman