Index-Organized Table experiences

From: Daniel Fink <Daniel.Fink_at_Sun.COM>
Date: Wed, 28 Apr 2004 08:14:50 -0600
Message-id: <408FBC5A.678E43E8@sun.com>

We are looking to implement IOTs for a couple of intersection entities in a 10g db. I would like to hear from those brave enough to actually use IOTs what is the good, the bad and the ugly.

example:

Employee (heap table)
Project (heap table)

There is a many-to-many relationship between the tables (1 employee can be on many projects and 1 project can have many employees).

The emp_project table is the intersection entity containing emp_id and project_id as the only columns. There are FK constraints on each of the columns. The combination of emp_id and project_id is unique.

This situation *sounds* like the right one for an IOT, otherwise we would have 1 table and 2 indexes (1 on each column).

My main concerns are:
1) Integrity/performance
2) Locking behavior (do I need to adhere to the traditional "index all foreign keys" rule to prevent excessive locking?) 3) Any especially nasty gotchas

Thanks,
Daniel

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.
--

Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html

Received on Wed Apr 28 2004 - 09:12:35 CDT