Transaction Scope
The scope of a transaction on the Analysis server is limited to a single cube. Transactions that contain updates to a single cube either commit or fail on the cube as a complete atomic operation.
Important Transactions that contain updates to more than one cube are not guaranteed to be atomic. In the case when a transaction contains updates that affect more than one write-enabled cube, it is possible for the updates to commit for some cubes but fail for others. This includes the case when updates are being applied to a virtual cube that contains more than one underlying write-enabled cube; it is possible for a transaction applied to the virtual cube to commit on one or more of the underlying cubes but fail on others.
If a transaction that includes updates to multiple cubes fails due to time-out, it is safe to attempt to commit the same transaction again. The transaction will be applied only to cubes that were not updated in the previous attempt. However, it is recommended that client applications use a separate transaction for each cube when updating multiple cubes.