To improve the performance of replicated partitions, follow these guidelines:
Do not replicate members that are dynamically calculated in the data source, because Essbase must probe the outline to find dynamically calculated members and their children to determine how to perform the calculation.
Do not replicate derived data from the data source. Instead, replicate the lowest practical level of each dimension and perform the calculations on the data target after you complete the replication.
For example, to replicate the database along the Market dimension:
Define the shared area as the lowest-level members of the Market dimension that you care about, for example, East, West, South, and Central and the level 0 members of the other dimensions.
After you complete the replication, calculate the values for Market and the upper-level values in the other dimensions at the data target.
Sometimes you cannot calculate derived data at the data target. In that case, replicate it from the data source. For example, you cannot calculate derived data at the data source if the data meets any of the following criteria:
Requires that data outside the replicated area be calculated.
Requires calculation scripts from which you cannot extract only the portion to be calculated at the data target.
Is being replicated onto a computer with little processing power, such as a laptop.
To optimize the replication of an aggregate storage database when the aggregate storage database is the target and a block storage database is the source and the two outlines are identical, use one of these methods:
The REPLICATIONASSUMEIDENTICALOUTLINE configuration setting in essbase.cfg. The setting can be enabled at the server, application, or database level. The syntax for the setting is as follows:
REPLICATIONASSUMEIDENTICALOUTLINE [appname [dbname]] TRUE | FALSE
When updating the essbase.cfg file, you must stop and then restart Essbase Server for the changes to take effect.
The alter database MaxL statement with the replication_assume_identical_outline grammar. The statement can be enabled only at the database level. The syntax for the statement is as follows:
alter database appname.dbname enable | disable replication_assume_identical_outline;
When using the alter database statement, you do not need to stop and restart the aggregate storage application.
Both optimization methods affect only the target aggregate storage application; the source block storage application is not affected. The methods do not apply to block storage replication.
Partitioning along a dense dimension takes longer than partitioning along a sparse dimension. When Essbase replicates data partitioned along a dense dimension, it must access every block in the data source and then create each block in the data target during the replication operation.
You cannot replicate data into a member that is dynamically calculated at the data target. Essbase does not load or replicate into Dynamic Calc and Dynamic Calc and Store members, because these members do not contain data until a user requests it at runtime. Essbase avoids sending replicated data for both dynamic dense and dynamic sparse members on the replication target, because this data is not stored on the data target.
To replicate only the data values that have changed instead of the entire partition, see Populating or Updating Replicated Partitions.