You can use the Linked Reporting Objects (LROs) feature to associate objects (also called artifacts) with data cells. The objects can be flat files, HTML files, graphics files, and cell notes. See Linking Objects to Essbase Data.
Two aspects of LROs affect disk space:
The size of the object. Because Essbase copies files used as LROs to the server, you must know the combined size of all files you are using as LROs.
You can set a limit on the size of a linked object, if the linked object is a file (as opposed to a cell note). See Limiting LRO File Sizes. |
The size of the LRO catalog, where the Essbase Kernel stores information about LROs. Cell notes and URLs are also stored in the catalog. A catalog entry is stored as an index page. For every catalog entry, Essbase uses 8 KB.
To estimate the disk space requirements for LROs:
Estimate the size of the objects. If a limit is set, multiply the number of LROs by that limit. Otherwise, sum the size of all anticipated LROs.
Size the LRO catalog. Multiply the total number of LROs by 8,192 bytes.
Add together the two areas and write the result of this calculation to the cell labeled DJ in Table 247, Worksheet: Estimate of Disk Requirements for a Database.
Assume the database uses 1,500 LROs, which comprise the following:
Perform the following calculations:
Multiply 1,000 * 512 bytes for 512,000 bytes maximum required for the stored URLs.
Calculate the size of the LRO catalog. Multiply 1,500 total LROs * 8,192 bytes = 12,288,000 bytes.
Add together the two areas; for example:
512,000 bytes + 12,288,000 bytes = 12,800,000 bytes total LRO disk space requirement
See also Block Storage Database Limits for Linked Reporting Objects considerations.