Transparent partitions can solve many database problems, but transparent partitions are not always the ideal partition type.
You need less disk space, because you are storing the data in one database.
The data accessed from the data target is always the latest version.
When the user updates the data at the data source, Essbase makes those changes at the data target.
Individual databases are smaller, so they can be calculated more quickly.
The distribution of the data is invisible to the end user and the end user’s tools.
You can load the data from either the data source or data target.
You can enable write-back functionality for aggregate storage databases by creating a transparent partition between an aggregate storage database as the source and a block storage database as the target.
See Using a Transparent Partition to Enable Write-Back for Aggregate Storage Databases.