Disadvantages of Transparent Partitions * Outline synchronization is required (D) If you make changes to one outline, the two outlines are no longer synchronized. Although Essbase makes whatever changes it can to replicated and transparent partitions when the outlines are not synchronized, Essbase may not be able to make the data in the data source available in the data target. Essbase tracks changes that you make to block storage outlines and provides tools to keep your block storage outlines synchronized. Note:Essbase does not enable automatic synchronization of aggregate storage outlines. You must manually make the same changes to the source and target outlines. * Transparent partitions increase network activity, because Essbase transfers the data at the data source across the network to the data target. Increased network activity results in slower retrieval times for users. (E) * Because more users are accessing the data source, retrieval time may be slower. (B) * If the data source fails, users at both the data source and the data target are affected. Therefore, the network and data source must be available whenever users at the data source or data target need them. * (C) When you perform a calculation on a transparent partition, Essbase performs the calculation using the current values of the local data and transparent dependents. Essbase does not recalculate the values of transparent dependents, because the outlines for the data source and the data target may be so different that such a calculation is inaccurate. To calculate all partitions, issue a CALC ALL command for each individual partition, and then perform a CALC ALL command at the top level using the new values for each partition. * Formulas assigned to members in the data source may produce calculated results that are inconsistent with formulas or consolidations defined in the data target, and vice versa. Note: Advantages of Transparent PartitionsTransparent 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. (not A) * 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.
Disadvantages of Transparent Partitions
* Outline synchronization is required (D)
If you make changes to one outline, the two outlines are no longer synchronized. Although Essbase makes whatever changes it can to replicated and transparent partitions when the outlines are not synchronized, Essbase may not be able to make the data in the data source available in the data target.
Essbase tracks changes that you make to block storage outlines and provides tools to keep your block storage outlines synchronized.
Note:
Essbase does not enable automatic synchronization of aggregate storage outlines. You must manually make the same changes to the source and target outlines.
* Transparent partitions increase network activity, because Essbase transfers the data at the data source across the network to the data target. Increased network activity results in slower retrieval times for users. (E)
* Because more users are accessing the data source, retrieval time may be slower. (B)
* If the data source fails, users at both the data source and the data target are affected. Therefore, the network and data source must be available whenever users at the data source or data target need them.
* (C) When you perform a calculation on a transparent partition, Essbase performs the calculation using the current values of the local data and transparent dependents. Essbase does not recalculate the values of transparent dependents, because the outlines for the data source and the data target may be so different that such a calculation is inaccurate. To calculate all partitions, issue a CALC ALL command for each individual partition, and then perform a CALC ALL command at the top level using the new values for each partition.
* Formulas assigned to members in the data source may produce calculated results that are inconsistent with formulas or consolidations defined in the data target, and vice versa.
Note: Advantages of Transparent Partitions
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. (not A)
* 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.