Archives of the TeradataForum

Message Posted: Fri, 07 Oct 2005 @ 14:56:57 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Hi Rachana,

Considerations for using join index

Can not Mload or FastLoad to tables that are part of an index.

Can not execute a delete all against tables that are part of a join index.

The join index must first be dropped and then the tables emptied.

Can not dump and restore tables that have a join index. The join index must first be dropped and then the tables dropped.

Updates against the tables in the Join index will take longer because the Join index also needs to be maintained.

Pros

Join index's contribute greatly to help improve performance. If there is an online transaction that runs often during the day which always joins the same two tables, a join index can help minimize CPU.

A single join index is also helpful when you want to have two primary indexes for the same table.

Let me know if you have further questions.

	<Prev	Next>		<<First	<Prev	Next>	Last>>