Determines the amount of memory that is reserved to cache queried members from a Hybrid Analysis Relational Source.
HAMEMORYCACHESIZE [appname [dbname]] n
appname—Optional. If you supply an application name, the setting applies to all databases within the named application. If you do not supply an application name, the setting applies to all applications and databases on the Essbase Server.
dbname—Optional. If you supply a database name and an application name, the setting applies only to the named database. If you do not also provide an application name, the database is ignored and the setting applies to all applications and databases on the Essbase Server.
n—An integer expressed in bytes (B), kilobytes (K), megabytes (M), or gigabytes (G)
Minimum value: 1048576 B (1 M). Any value less than this minimum value causes HAMEMORYCACHESIZE to default to 1 M.
Default value: 1 megabytes (1 M, which is 1048576 bytes)
If a value is given without a B, K, M, or G qualifier, it is assumed the value is in bytes.
The qualifier can be in upper or lowercase and can be entered adjacent to the value (10M) or separated by a space (10 M).
This setting sizes the memory buffer that holds relational data during the execution of spread sheet or report scripts that drill into Hybrid Analysis Relational Sources. When you specify the cache size, you control the memory used to cache relational members during execution. A larger cache size optimizes the usage of relational members during execution and increases the speed of metadata retrieval from the metaoutline. Thus, more memory allocated to the cache means fewer SQL queries to resolve member names, resulting in improved performance.
In order to have configuration parameters applied to the application level, the global value must be defined first, and the application level value must be defined second (see Example 2 below).
HAMEMORYCACHESIZE 1M
In the following example, all databases in the application "Test" have a cache value of 1500K, and all other applications have a cache value of 2M.
HAMEMORYCACHESIZE 2M HAMEMORYCACHESIZE Test 1500K
In the following example, all applications and databases have a cache value of 2M because the application cache value is overriden.
HAMEMORYCACHESIZE Test 1500K HAMEMORYCACHESIZE 2M
This ordering is needed only for global and unspecified (untitled) applications.