You are on page 1of 24

Data Block and Block

A Data Block is used to store the data. The Data Block represents all dense dimension members for its combination of sparse dimension members. Index entry is created for each Data Block, which is used to access the data in the datablock.

Block Size
Block Size = multiplication of dense dimension members (stored members)* 8 Ex: Accounts 5 members
Time 10 members Scenario 3 members Then block size is 5*10*3*8 = 1200 Note: Default range of block size is 8kb to 100kb (in windows) and 8kb to 180kb (in unix)

Block Size
Potential no. of data blocks is = Total no. of sparse dimension members. The number of existing data blocks is usually less than the potential no. of data blocks. Outline size = Total number of members under outline * Size of member name (350 to 450 bytes)

All Sparse Dimensions


In this case Essbase creates data blocks that consist of single data cells that contain single data values. An index entry is created for each data block. This configuration produces a huge index that requires a large amount of memory. The more index entries, the longer Essbase searches to find a specific block.

All Dense Dimensions


In this case Essbase creates one index entry and one very large block. Essbase needs to load the entire block into memory when it searches for a data value, which requires enormous amounts of memory.

Combination of Dense and Sparse dimensions


Essbase creates data blocks for combinations of members in the sparse standard dimensions providing at least one data value exists for the member combination. In this case the data blocks are created only for all data values existed and this you can retrieve and store data efficiently.

Data files
Files in which Analytic Services stores data values in data blocks in data files. Essbase names these files with
ESSxxxxx.PAG where xxxxx is a number which starts with 00001 and ends with 65535

Note: A Data block is a subdivision of a data file.

Index files
Files that Analytic Services uses to retrieve data blocks from data files. Ex: Essbase names with essxxxxx.ind, where xxxxx is a number which starts with 00001 and ends with 65535

Data and Index file sizes


Essbase automatically allocates sizes for data and index files. The maximum limit for each file is 2GB and once after reaching 2GB it will create a new file with different name. Ex: ESS00001.PAG, once after reaching 2GB it will create another file with ESS00002.PAG and same for .IND file.

Index pages
Index page is a subdivision of an index file. It contain index entries that point to data blocks. The size of index pages is fixed at 8 KB.

Index cache
A buffer in memory that holds index pages. Analytic Services allocates memory to the index cache at startup of the database. Default size is 1024kb

Data file cache


A buffer in memory that holds compressed data files. Analytic Services allocates memory to the data file cache during data load, calculation, and retrieval operations, as needed. Default size is 32768KB

Data cache
A buffer in memory that holds uncompressed data blocks. Analytic Services allocates memory to the data cache during data load, calculation, and retrieval operations, as needed. Default size is 3072KB

Calculator cache
A buffer in memory that Analytic Services uses to create and track data blocks during calculation operations.

Dynamic Calculator Cache


This cache holds the blocks while calculating the Dynamic calc members during retrieval. To see the cache settings
Double click on the properties under database & click caches tab.

ASO
Aggregate storage database is called as ASO. The essbase database storage model supporting large-scale, sparsely distributed data, which is categorized into many, potentially large dimensions. Selected data values are aggregated and stored, typically with improvements in aggregation time.

BSO
Block Storage Database is also called as BSO. The essbase database storage model categorizing and storing data based on the sparsity of data values defined in sparse dimensions. Data values are stored in blocks, which exist only for sparse dimension for which there are values.

ASO
1)Support rapid aggregation, optimized to support high dimensionality and sparse data. 2)Only one database supported per application.

BSO
1) Multiple blocks defined by dense and sparse dimensions and their members, optimized for financial applications. 2)More than one database can be created per application.

ASO BSO (for account dimensions and members)


4) No time balance members 5) No two-pass calculation 6) No association of attribute dimensions with the dimension tagged as accounts 4) Supports
5) Supports 6) Supports

ASO BSO (for stored members)


7) Supports only + (addition) and ~(ignore of no consolidation) operators 8) NO DTS 7)It supports all consolidation properties

8)Supports DTS

ASO
Calculation Scripts are not supported Attribute calculations dimensions support for sum

BSO
Calculation scripts are supported Supports sum, count, min, max and average

Batch process
Batch process is a method of using ESSCMD to write a batch file or a shell script file that can be used during automation of server maintenance and diagnostic tasks.

Batch File
Batch file is an operating system file (windows or unix) that can call multiple ESSCMD scripts and run multiple sessions of ESSCMD. Windows based batch file will have file extension as .bat In unix batch file will be written as a shell script.

You might also like