Databases Reference
In-Depth Information
•
CALCLIMITFORMULARECURSION
: Now here is a little known setting. What it
does is prevent the server from executing calculation scripts that perform
recursive operations deeper than the system specified number of 31 levels.
If you add this setting to the
essbase.cfg
file with a
TRUE
parameter, the
system will enforce the 31 level rules. If you add this setting with a
FALSE
parameter, there will be no limit, and a lowly database calculation script
could actually be responsible for bringing down your analytic server. Try
explaining that to your boss! Besides, rarely do you code a calculation script
that even uses half that many levels.
•
DATACACHESIZE
: This sets the data cache size for all of the new databases
that are created on the server. This cache holds the data blocks in memory.
This cache setting is not applied to all of the existing databases that are
already created on the server. The data cache size can be specified in Bytes (B),
Kilobytes (K), Megabytes (M), or Gigabytes (G). This will take place after
the analytical service is restarted or after the server reboot.
Syntax:
DATACACHESIZE n
n is an integer value in B, K, M, or G
Code Sample:
DATACACHESIZE 4M
This sets the data cache size to 4 Megabytes for all new databases that are
created after the service is restarted with this setting.
•
DATAFILECACHESIZE
: This sets the data file cache size for all of the new
databases that are created on the server. This cache holds the data files in
the memory. The data file cache size can be specified in Bytes (B), Kilobytes
(K), Megabytes (M), or Gigabytes (G). This will take place after the analytic
service is restarted or after a server reboot.
Syntax:
DATAFILECACHESIZE n
n is an integer value in B, K, M, or G
Code Sample:
DATAFILECACHESIZE 400M
This sets the data file cache size to 400 Megabytes for all of the new databases
that are created after the service is restarted to have a data file cache size
of 400 MB.
