To enhance performance, Microsoft® Repository transactions normally run in write-back mode. In write-back mode, a transaction's updates are held in the Repository cache until the transaction is committed. If a single transaction performs a large number of updates, it can cause the Repository cache for the process to overflow.
By setting transaction options through the SetOption method, a Repository instance can operate in exclusive write-back mode, where it allows no more than one active transaction at a time for a given process and Microsoft Repository database. Using exclusive write-back mode will reduce, but not eliminate, the possibility of a cache overflow. For a very large number of updates within a single transaction, or if memory is limited, the Repository cache can still overflow.
To guarantee that cache overflows will not cause transactions to fail, set the exclusive write-through mode transactional option. In exclusive write-through mode, updates are immediately flushed from the Repository cache. Exclusive write-through mode does not affect your ability to cancel an active transaction using the Abort method.