1. A non-persistent internal transaction dataset should only be used if you are sure transactions will never involve records from a persistent Dataset. Using a non-persistent internal transaction dataset when appropriate can provide better performance however. For the most reliable behavior, datasets enrolled in transactions should use the same persistence mechanism as the TransactionController itself.

2. Read-only transactions should be used for transactions with no write operations to get better performance.

3. A TransactionAction or TransactionBiAction should only use the provided transaction resources. Transactional guarantees are provided only for the operations performed through the added resources.

4. Avoid executing transactions using External Transaction Control (see the description in the section Executing Using an ExecutionBuilder). This form of executing is significantly more error prone than the recommended functional forms.