Essbase uses the calculator cache to create and track data blocks during calculation. Using the calculator cache significantly improves your calculation performance. The size of the performance improvement depends on the configuration of your database. You can choose one of three levels - high low default. You will have the additional resources in play to speed up the process.
|Published (Last):||1 June 2010|
|PDF File Size:||5.98 Mb|
|ePub File Size:||12.91 Mb|
|Price:||Free* [*Free Regsitration Required]|
A database contains two types of values: Values that you enter, called input data Values that are calculated from input data For example: You enter regional sales figures for a variety of products.
You calculate the total sales for each. You enter the budget and actual values for the cost of goods sold for several products in several regions. You calculate the variance between budget and actual values for each product in each region. The database contains regional sales figures and prices for all products. Small differences in the precision of cell values may occur between calculations run on different platforms, due to operating system math library differences.
Note: Most computers represent numbers in binary, and therefore can only approximately represent real numbers. Because binary computers cannot hold an infinite number of bits after a decimal point, numeric fractions such as one-third 0. Fractions with a denominator of the power of two for example, 0. Essbase offers two methods for calculating a database: Outline calculation Calculation script calculation The method that you choose depends on the type of calculation that you want to perform.
Outline Calculation Outline calculation is the simplest calculation method. Essbase bases the calculation of the database on the relationships between members in the database outline and on any formulas that are associated with members in the outline. Basic database.
You can use dynamic calculations to calculate data at retrieval time. See Dynamically Calculating Data Values. Calculation Script Calculation Calculation script calculation is the second method of calculation.
Using a calculation script, you can choose exactly how to calculate a database. For example, you can calculate part of a database or copy data values between members.
A calculation script contains a series of calculation commands, equations, and formulas. The example displays only the members in Qtr1—Jan, Feb, and Mar.
The Scenario dimension has two child members—Budget for budget values and Actual for actual values. An intersection of members one member on each dimension represents a data value. Actual, Sales Slice of the Database To refer to a specific data value in a multidimensional database, you must specify each member on each dimension. A data value is stored in one cell in the database. For information about how Essbase calculates a database, see Defining Calculation Order.
You can, however, specify any calculation script as the default database calculation. Thus, you can assign a frequently used script to the database rather than loading the script each time you want to perform its calculation. If you want a calculation script to work with calculation settings defined at the database level, you must set the calculation script as the default calculation.
To set the default calculation, use a tool: Tool.
Join the world’s largest interactive community dedicated to Oracle technologies.
CL Apr 1, AM in response to Kevin, While it does not remove empty blocks, the true definition of fragmentation in the documentation is "empty space", not "empty blocks" Surely better to get rid of it and have that many fewer blocks in the BSO database, empty or not. Remember, Essbase orders blocks, but uses the its index to grab the blocks it needs for calculations or retrieves. The fewer trips to the disk, and the closer the relevant data is for whatever the operation might be the faster the process. This is the whole actual blocks versus potential blocks concept. Per the DBAG: Fragmentation is created when Essbase writes a data block to a new location on disk and leaves unused space in the former location of the data block. Block size increases because data from a data load or calculation is appended to the blocks; the blocks must therefore be written to the end of a data file.