Its not really the index type, as all indexes can be spread across
many devices to minimize IO wait times for index IO. Its the
tablespace that you create the indexes in that allows you to spread
the index across multiple devices. You should create your table in a
DMS tablespace, placing data in one tablespace and indexes into a
separate tablespaces (note that even if you mixed data and indexes in
the same tablespace, you could spread that tablespace across multiple
devices). Create the tablespace with multiple containers, one
container on each device (or filesystem, where each filesystem you
use is on a separate device).

James
Fourth Millennium Technologies,
www.fmtusa.com

At 07:28 AM 4/26/2007, Khan Nadeem wrote:

>Hi Gurus,
>
>
>
>What index type could be used for spreading an index across many table
>spaces, decreasing contention for index lookup and for increasing
>scalability and manageability?
>
>
>
>
>
>Nadeem
>
>
>
>This message contains information that may be privileged or
>confidential and is the property of the Capgemini Group. It is
>intended only for the person to whom it is addressed. If you are not
>the intended recipient, you are not authorized to read, print,
>retain, copy, disseminate, distribute, or use this message or any
>part thereof. If you receive this message in error, please notify
>the sender immediately and delete all copies of this message.
>
>
>---------------------------------------------------------------------
>TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
>To post a dba job: http://jobs.lazydba.com
>To Subscribe : http://www.LazyDBA.com
>To unsubscribe: http://www.lazydba.com/unsubscribe.html


DB2 & UDB email list listserv db2-l LazyDBA home page