Glossary Term | Glossary Definition |
---|---|
The activity of summarizing and consolidating records is often called aggregation in the technical vocabulary of database experts. Aggregation simply means that data is grouped and summarized to dramatically improve the performance of high-level queries. | |
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 members for which there are values. | |
Logical expressions or formulas that are created within an application to produce a desired set of resulting values. | |
A set of commands that define how a database is consolidated or aggregated. A calculation script may also contain commands that specify allocation and other calculation rules separate from the consolidation process. | |
The process of aggregating or of running a calculation script on a database. | |
The process of aggregating data, or of running a calculation script on a database. | |
A module of Enterprise Performance Management Architecture (EPMA) that Planning and Financial Management users can use to design, validate, and administrate business rules in a graphical environment. c | |
(1) The data value at the intersection of dimensions in a multidimensional database; the intersection of a row and a column in a worksheet. (2) A logical group of nodes belonging to one administrative domain. | |
A set of circumstances that must take place to be true. | |
The process of aggregating data from dependent entities to parent entities. For example, if the dimension Year consists of the members Qtr1, Qtr2, Qtr3, and Qtr4, its consolidation is Year. | |
A block of data that contains three or more dimensions. An Essbase database is a cube. | |
See outline. | |
In block storage databases, a dimension likely to contain data for every combination of dimension members. For example, time dimensions are often dense because they can contain all combinations of all members. Contrast with sparse dimension. | |
A data category used to organize business data for retrieval and preservation of values. Dimensions usually contain hierarchies of related members grouped within them. For example, a Year dimension often includes members for each time period, such as quarters and months. | |
A calculation script that may contain values for runtime prompts. | |
A combination of operators, functions, dimension and member names, and numeric constants calculating database members. | |
A routine that returns values or database members. | |
The process of running a business rule, calculation script, or sequence against a database to return calculated values. | |
A member that has no children. | |
A discrete component within a dimension. A member identifies and differentiates the organization of similar units. For example, a time dimension might include such members as Jan, Feb, and Qtr1. | |
A set of data that defines and describes the properties and attributes of the data stored in a database or used by an application. Examples of metadata are dimension names, member names, properties, time periods, and security. | |
A method of organizing, storing, and referencing data through three or more dimensions. An individual value is the intersection point for a set of dimensions. Contrast with relational database. | |
The database structure of a multidimensional database, including all dimensions, members, tags, types, consolidations, and mathematical relationships. Data is stored in the database according to the structure defined in the outline. | |
A set of values including upper and lower limits, and values falling between limits. Can contain numbers, amounts, or dates. | |
A "two-dimensional" database made up of tables of information. Two or more tables can be cross-referenced to generate a new table. A database that has only one table is called a flat file database. Compare with multidimensional database. | |
Stores metadata, formatting, and annotation information for views and queries. | |
A variable that users enter or select before a business rule is run. | |
An explicitly defined set of members across multiple dimensions. This selection does not change as the dimension is maintained. | |
A dimension for classifying data; for example, Actuals, Budget, Forecast1, and Forecast2. | |
Part of the Shared Services database, the Shared Services Registry stores and reuses information for most installed Hyperion products, including installation directories, database settings, deployment settings, computer names, ports, servers, URLs, and dependent service data. | |
In block storage databases, a dimension unlikely to contain data for all member combinations when compared to other dimensions. Contrast with dense dimension. For example, not all customers have data for all products. | |
A sequence of characters treated as a unit. | |
A predefined format designed to retrieve particular data consistently. | |
User-defined attribute, associated with members of an outline to describe a characteristic of the members. Users can use UDAs to return lists of members that have the specified UDA associated with them. | |
A process of checking a business rule, report script, or partition definition against the outline to make sure that the object being checked is valid. |