>The standard answer, however, is the following scenario: Monday through
>Friday the database observers itself pumping transactions and decides
>to reorganize itself Friday night. Saturday the week end batch streams
>start, optimized for pumping transactions and pessimized for batch.
>Sunday night, the database realizes it has made a dreadful mistakes
>and re-organizes itself optimized for batch and pessimized for
>transactions. Sigh. Can't win. Database gives up the automatic
>optimization, marries a web server, and retires to the Bahama to drive
>illegal web gambling.

So allow the DBA to configure this feature. And/or add a transaction
parameter to tell the database to ignore the transaction for purposes of
computing index usage.

-Mark