Database Properties Window—Transactions Tab

For block storage databases, you use the Transactions tab to specify when Essbase writes data to disk and to control the level of data access among multiple, concurrent users.

To enable transactions to hold read/write locks on all data blocks involved with a transaction until the transaction completes and commits, you select the “Committed access" option and then specify a concurrency option:

To enable transactions to hold read/write locks on a block-by-block basis, you select the “Uncommitted access” option (the default setting) and then specify when Essbase performs a commit operation:

If the value of “Commit blocks” or “Commit rows” is not zero, Essbase commits data when it reaches the first threshold. For example, if “Commit blocks” is 10, “Commit rows” is 0, and data is loaded, Essbase commits after 10 blocks are updated. If “Commit blocks” is 5, “Commit rows” is 5, and data is loaded, Essbase commits after 5 rows are loaded or 5 blocks are updated, whichever happens first.

Note:

To ensure seamless recovery, Essbase retains duplicate data until it commits. You should allow disk space for double the size of your database to accommodate duplicate data, particularly if you use committed access or if the “Commit blocks” and “Commit rows” values are 0.

Note:

This tab does not apply to aggregate storage databases.

Related Information

Related Commands