Hi,

Different sources recommend to de-activate indices (and if applicable
also triggers) before running batch inserts and updates, then
re-activate them after the batch job.

The reason is that it's more efficient to rebuild the index once after
the data rows are in place, rather to update it incrementally for each
insert.

What isn't specified anywhere that I could find, is what happens in a
multi-user environment. Specfically:

1. Are the commands to de/activate indices and triggers executed in a
transaction context?

2. If yes, then what happens if there are several transactions and in
one of them an index is de-activated? Will the other transactions
continue to "see" and use that index?

3. Is there any way to de/activate constraint enforcing indices?

Thanks,

Eyal.