Glossary Term | Glossary Definition |
---|---|
See missing data. | |
A dimension type that makes accounting intelligence available. Only one dimension can be defined as Accounts. | |
In Essbase Integration Services, a state in which you can draw lines to define joins between objects in the OLAP model. | |
The integration of a relational database with an Essbase multidimensional database so that all data remains in the relational database and is mapped to summary-level data in the Essbase database. | |
A cell comprising several cells. For example, a data cell that uses Children(Year) expands to four cells containing Quarter 1, Quarter 2, Quarter 3, and Quarter 4 data. | |
The database storage model designed to support large-scale, sparsely distributed data which is categorized into many, potentially large dimensions. Upper level members and formulas are dynamically calculated, and selected data values are aggregated and stored, typically with improvements in overall aggregation time. | |
A collection of aggregate cells based on the levels of the members within each dimension. To reduce calculation time, values are pre-aggregated and stored as aggregate views. Retrievals start from aggregate view totals and add up from there. | |
The process of rolling up and storing values in an aggregate storage database; the stored result of the aggregation process. | |
See consolidation level. | |
In Essbase Integration Services, a column in the data source that contains the aliases for a member level in the metaoutline. | |
A table that contains alternate names for members. | |
A hierarchy of shared members. An alternate hierarchy is based upon an existing hierarchy in a database outline, but has alternate levels in the dimension. An alternate hierarchy allows the same data to be seen from different points of view. | |
See alias. | |
A branch member that has members below it. For example, the members Qtr2 and 2006 are ancestors of the member April. | |
1) A software program designed to run a specific task or group of tasks such as a spreadsheet program or database management system; 2) A related set of dimensions and dimension members that are used to meet a specific set of analytical requirements, reporting requirements, or both. | |
See Essbase Integration Services Console. | |
A characteristic of a dimension member. For example, Employee dimension members may have attributes of Name, Age, or Address. Product dimension members can have several attributes, such as a size and flavor. | |
A standard dimension that is associated with one or more attribute dimensions. For example, assuming products have flavors, the Product dimension is the base dimension for the Flavors attribute dimension. | |
The primary storage unit which is a multidimensional array representing the cells of all dense dimensions. | |
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. | |
A member of a hierarchy that may or may not contain leaf members. | |
See Essbase Integration Services Console. | |
See OLAP Metadata Catalog. | |
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 member with a parent above it in the database outline. | |
A mapping of bit combinations to a set of text characters. Different code pages support different sets of characters. Each computer contains a code page setting for the character set requirements of the language of the computer user. In the context of this document, code pages map characters to bit combinations for non-Unicode encodings. See also encoding. | |
See Essbase Integration Services Shell. | |
An operation that joins two characters or strings in the order specified, forming one string whose length is equal to the sum of the lengths of the two characters or strings. For example, the strings "New York " and "Library", when concatenated, become "New York Library". | |
In relational databases, a data extraction criterion. For example, you can apply a condition to extract only the data that begins with the letter A. | |
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. | |
The top of an aggregation hierarchy or any branch or sub-branch below the top, including the input (leaf) portion of the hierarchy. | |
A process that converts currency values in a database from one currency into another. For example, to convert one U. S. dollar into the European euro, the exchange rate (for example, 0.923702) is multiplied by the dollar (1* 0.923702). After conversion, the European euro amount is .92. | |
The process of making inconsistent data consistent. Examples of inconsistent data are data in which some values are incorrect or not of the correct data type. | |
A set of criteria that determines how to load data from a text-based file, a spreadsheet, or a relational data set into a database. | |
See cell. | |
See outline. | |
A set of instructions that defines how to change or reformat a relational database DateTime data type to your choice of date format. | |
The process of adding redundancy to data in a database, typically by joining tables to form more complete sets of data in the individual tables. This process is performed for the purpose of increasing data retrieval performance. Contrast with normalization. | |
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. | |
Any member below a parent in the database outline. In a dimension that includes years, quarters, and months, the members Qtr2 and April are descendants of the member Year. | |
See leaf member. | |
A data category used to organize business data for the 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 collection of dimension tables organized in a hierarchical structure, with one of the dimension tables joined directly to the fact table. A dimension branch defines a single, potential dimension in an Essbase Integration Services metaoutline. | |
In Essbase, a set of operations similar to data load rules. Instead of loading data, the dimension build rules modify the outline based on data in the external data source file. | |
1) A table that includes numerous attributes about a specific business process; 2) In Essbase Integration Services, a container in the OLAP model for one or more relational tables that define a potential dimension in Essbase. | |
A dimension property that enables the use of predefined functionality. Dimensions tagged as time have a predefined calendar functionality. | |
Direct access by Spreadsheet Add-in users to data stored in the relational data source. Defined in Essbase Integration Services, a drill-through report is based on intersection levels (member sets) that Spreadsheet Add-in users double-click to view detail information that is not stored in the Essbase database. | |
The second occurrence of a member name in a data source. Users can determine whether Essbase Integration Server supports duplicate members, ignores duplicate members, or adds them as shared members. See also shared member. | |
Multiple occurrences of a member name in a database, with each occurrence representing a different member. For example, a database has two members named New York. One member represents New York state and the other member represents New York city. | |
A database outline containing duplicate member names. | |
Members in a block storage outline that Essbase calculates only upon the first retrieval of the value. Essbase then stores the calculated value in the database. Subsequent retrievals do not require calculating. | |
Members in a block storage outline that Essbase calculates only at retrieval time. Essbase discards calculated values after completing the retrieval request. | |
In Essbase, a calculation that occurs only when you retrieve data on a member that is tagged as Dynamic Calc or Dynamic Calc and Store. The member's values are calculated at retrieval time instead of being precalculated during batch calculation. | |
A process that performs period-to-date reporting in block storage databases. | |
A method for mapping bit combinations to characters for creating, storing, and displaying text. Each encoding has a name; for example, UTF-8. Within an encoding, each character maps to a specific bit combination; for example, in UTF-8, uppercase A maps to HEX41. See also code page, locale. | |
The server component of the Essbase Integration Services product family. Essbase Integration Services uses the information stored in the OLAP Metadata Catalog to extract the dimension names and members names needed to build an Essbase outline from the data source. When the Essbase outline is complete, Integration Server extracts data from the data source, performs the operations specificed in the metaoutline, and loads the data into the Essbase database. | |
The client component of the Essbase Integration Services product family. This graphic interface tool is used to create OLAP models and metaoutlines, and to load data into an Essbase database. | |
In Essbase Integration Services, a command-line tool that you can use to perform common operations on the Essbase outline and the data in the Essbase database. For example, you can use the LOADDATA command to load data. | |
See Essbase Server. | |
See outline. | |
A repository of data within Essbase that contains a multidimensional data storage array. Each database consists of a defined storage structure (a database outline), data, security definitions, and other associated files, such as calc scripts or data load rules. See also application. | |
An optional configuration file for Essbase. Administrators may edit this file to customize Essbase Server functionality. Some configuration settings may also be used with Essbase clients to override Essbase Server settings. | |
The Essbase environment variable that defines the encoding used to interpret text characters. See also encoding. | |
A container for one or more relational tables that define the data values for each dimension intersection in the OLAP model. For example, if the OLAP model contains Products, Region, and Year dimensions, the fact table might include data values for the number of units of Product A sold in New York in January. | |
A character, such as a comma or tab, that separates fields in a data source. | |
A constraint on data sets that restricts values to specific criteria; for example, to exclude certain tables, metadata, or values, or to control access. | |
In relational databases, a column whose data values correspond to the values of a key column in another relational table. See also key column, primary key. | |
A layer in a hierarchical tree structure that defines member relationships in a database. Generations are ordered incrementally from the top member of the dimension (generation 1) down to the child members. Use the unique generation name to identify a layer in the hierarchical tree structure. | |
An analysis mapping low-level data stored in a relational database to summary-level data stored in Essbase, combining the mass scalability of relational systems with multidimensional data. | |
See Essbase Integration Services Console. | |
1) In Essbase, a method of retrieving data based on sparse dimensions. Also refers to the index files, collectively; 2) In relational databases, pointers that are logically arranged by the values of a key. Indexes optimize access to relational data. | |
In Essbase, a buffer in memory that holds index pages. | |
In Essbase, a pointer to an intersection of sparse dimensions. Each index entry points to a block on disk and locates a particular cell within the block by means of an offset. | |
In Essbase, a file used to store data retrieval information. It resides on disk and contains index pages. | |
In Essbase, a subdivision of an index file containing entries that point to data blocks. | |
Any data that is loaded from a data source and is not generated by calculation. | |
In relational databases, a rule stating that each row should have an entry for each required key column. | |
In Essbase Integration Services, procedural help displayed in a dockable window that accompanies the OLAP Model and OLAP Metaoutline main windows. Intelligent Help provides numbered procedures and links to new automatic-detection options and frequently used functions. | |
In Essbase Spreadsheet Add-in, an Essbase member combination that defines a specific value. For example, the member combination Actual, Root Beer, Sales, Jan, East represents the actual January sales value for root beer in the Eastern region. | |
A link between two relational database tables or topics based on common content in a column or row. A join typically occurs between identical or similar items within different tables or topics. For example, a record in the Customer table is joined to a record in the Orders table because the Customer ID value is the same in each table. | |
In Essbase Integration Services, two relational table columns that are joined from one table to another. | |
In relational databases, a column or columns that form a unique identifier for each row. For example, EMPLOYEE_ID might be a key column. | |
(1) In the Essbase Integration Services Console OLAP Metaoutline main window, the area on the left that enables you to view a list of dimensions previously defined in the OLAP model. (2) In the OLAP Model main window, the area on the left that displays a list of the tables and views available in a source relational database. | |
A layer in a hierarchical tree structure that defines database member relationships. Levels are ordered from the bottom dimension member (level 0) up to the parent members. | |
A data block for combinations of sparse, level 0 members. | |
A member that has no children. | |
In Essbase Integration Services, a member in a user-defined dimension into which data is loaded. Only user-defined dimensions require load members. For all non user-defined dimensions, Essbase Integration Server knows how to load members and data into the Essbase database. | |
In Essbase Integration Services, a set of rules that determine what actions the product performs on member level names and data as they are loaded. | |
A computer setting that specifies a location's language, currency and date formatting, data sort order, and the character set encoding used on the computer. Essbase uses only the encoding portion. See also encoding, ESSLANG. | |
In Essbase Integration Services, a column created by manipulating the data in one or more physical columns. Contrast with physical column. See also column. | |
In relational databases, a table created by manipulating columns from one or more physical tables. The logical table is only a view of the data; the columns remain stored in the original tables and are not physically duplicated in the logical table. Contrast with physical table. See also view. | |
A symbol that defines how data is calculated in formulas and outlines. Can be any of the standard mathematical or Boolean operators; for example, +, -, *, /, and %. | |
See multidimensional database. | |
Data values that a user wants to track, such as Unit_Price and Discount. By default, measures values map to the accounts dimension in the OLAP model, which maps to the measure dimension in the OLAP metaoutline, which in turn maps to the accounts dimension in the Essbase outline. | |
In Essbase Integration Services, a dimension that, by default, maps to the accounts dimension in the Essbase outline. | |
A discrete component within a dimension. A member identifies and differentiates the organization of similar units. For example, a time dimension might include members Jan, Feb, and Qtr1. | |
In Essbase, a list of member names used to specify a set of data at the intersection of two or more dimensions. A member combination is specified by using the cross-dimensional operator -> (a hyphen followed by a right-angle bracket). For example, the actual sales data for the month of January in Sample Basic is Sales->Jan->Actual. | |
A hierarchical level of detail within a dimension. For example, in a dimension that defines geographic areas by nation, which are then subdivided into provinces, the nation and province categories each represent a member level. A member level corresponds to a level in an Essbase outline. The measures dimension contains actual members that are also member levels. | |
In Essbase Integration Services, the process of adding dimensions and members (without data) to Essbase outlines. | |
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. | |
In Essbase Integration Services, a template containing the structure and rules for creating an Essbase outline from an OLAP model. | |
A marker indicating that data in the labeled location does not exist, contains no value, or was never entered or loaded. For example, missing data exists when an account contains data for a previous or future period but not for the current period. | |
In Essbase Integration Services, a state in which you can pick up, move, and drop objects in the OLAP Model main window. | |
Describes a method of referencing data through three or more dimensions. An individual data value is the intersection of one member from each dimension. | |
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 process of grouping and removing redundancy from data so that each entity is in its appropriate place in the database and only in its appropriate place. Contrast with denormalization. | |
In Essbase Integration Services, a set of instructions that define how to change or reformat a relational database numeric field type. For example, you may choose to divide numeric data by 100. | |
Open Database Connectivity. A database access method used from any application regardless of how the database management system (DBMS) processes the information. | |
See Essbase Integration Services Console. | |
See Essbase Integration Services Console. | |
See OLAP Metadata Catalog. | |
See Essbase Integration Services Shell | |
See Essbase Integration Server. | |
In Essbase Integration Services, a relational database containing metadata describing the nature, source, location, and type of data that is pulled from the relational data source. | |
In Essbase Integration Services, a logical model (star schema) that is created from tables and columns in a relational database. The OLAP model is then used to generate the structure of a multidimensional database. See also online analytical processing (OLAP). | |
See online transaction processing. | |
A multidimensional, multiuser, client-server computing environment for users who analyze consolidated enterprise data in real time. OLAP systems feature drill-down, data pivoting, complex calculations, trend analysis, and modeling. | |
OLTP applications are commonly referred to as data capture, data entry, or data collection applications. OLTP applications enable an organization to capture the large amounts of data resulting from its daily activities but provide limited capability for reporting on the data. | |
Standardized application programming interface (API) technology that allows applications to access multiple third-party databases. | |
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. | |
In Essbase Integration Services, a feature that allows you to use functions specific to your relational database management system (RDBMS) to extract data values for columns. You can provide a statement that Essbase Integration Server passes through to your RDBMS as a part of the SQL SELECT statement. You provide the statement as a property of a column and the pass-through feature returns a value for the column. | |
A special privilege that must be assigned to users or groups to enable them to access or modify secure data. Permissions include Read, Read/Write and None. | |
A column that is stored in a relational database. See also column. Contrast with logical column. | |
A combination of rows and columns stored in a relational database. Contrast with logical table. | |
In relational databases, a data element indicating the location of data in storage. | |
A dimension table that joins directly to the fact table. Additional dimension tables may join to the primary dimension table to create a dimension branch. | |
In relational databases, a column (key) that uniquely identifies a row. For example, Employee_ID. | |
An Essbase Integration Server parameter or Essbase Server configuration setting that controls the duration and size of queries made to data sources. | |
A set of information in a data source. Records are composed of fields, each of which contains one item of information. A set of records constitutes a table. A single record constitutes a row in the table. For example, a table containing personnel information might contain records (rows) that have three fields: a NAME field, an ADDRESS field, and a PHONE_NUMBER field. | |
A relational source table that contains information in one row that is a parent or child of information in another row. For example, in a relational source table containing the columns EMPLOYEE_ID, NAME, and MANAGER_ID, the columns EMPLOYEE_ID and MANAGER_ID are recursive because MANAGER_ID refers back to the EMPLOYEE_ID. Using Essbase Integration Services, you can build an Essbase outline hierarchy from a recursive source table. | |
A type of database that stores data in related two-dimensional tables. Contrast with multidimensional database. | |
In Essbase, an operation to regenerate or rebuild the database index and, in some cases, the data files. | |
In the Essbase Integration Services Console OLAP Metaoutline main window, the area on the right, in which you build a metaoutline. In the OLAP Model main window, the area on the right, in which you build an OLAP model. | |
See consolidation. | |
In relational databases, a logical model that represents the data and the relationships between the data. | |
A member that shares storage space with another member of the same name, preventing duplicate calculation of members that occur multiple times in an Essbase outline. | |
The part of the Shared Services repository that manages EPM System deployment information for most EPM System products, including installation directories, database settings, computer names, ports, servers, URLs, and dependent service data. | |
A child member at the same generation as another child member and having the same immediate parent. For example, the members Florida and New York are children of East and each other's siblings. | |
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. | |
See Structured Query Language. | |
In Essbase Integration Services, a function that enables editing of the standard SQL statements generated by Integration Server for drill-through reports. ODBC SQL, Native SQL, and stored procedures can be used when editing the standard SQL. The edited, user-defined SQL can be selected to improve data load performance when loading data into an Essbase database. | |
A database that you create to meet the needs of a specific application. A staging area is a snapshot or restructured version of one or more RDBMS. | |
A dimension that is not an attribute dimension. | |
A logical model that represents your relational data in a form that mirrors that of OLAP data. A star schema contains a fact table and one or more dimension tables. | |
A sequence of characters treated as a unit. | |
A computer language used to access data in relational databases. | |
An alternate name for an object, such as a table or a view, in a relational database management system (RDBMS). Some RDBMSs use the term "alias" to refer to a synonym. Not all RDBMSs support synonyms. | |
In relational databases, a form of data storage in which data is stored in records comprised of fields. Each record is defined by a unique, or primary, key. | |
In Essbase Integration Services, a set of instructions that define how to change or reformat the member names and data you extract from the source relational database. | |
An Essbase property that is used to recalculate members that are dependent on the calculated values of other members. Two-pass members are calculated during a second pass through the outline. | |
A mathematical indicator (+, -, *, /, %) associated with an outline member. The unary operator defines how the member is calculated during a database roll-up. | |
An Essbase application wherein character text is encoded in UTF-8, enabling users with computers set up for different languages to share application data. | |
An SQL command that is a type of join that combines the results of two SELECT statements. A union is often used to merge lists of values contained in two tables. | |
An attribute, associated with members of an outline to describe a characteristic of the members, that can be used to return lists of members that have the specified associated UDA. | |
Dimensions that you explicitly create in Essbase Integration Services, rather than dimensions obtained or built from the relational data source. | |
Members that you explicitly create in Essbase Integration Services, rather than obtaining and building them from the relational data source. | |
Logical tables that you create in Essbase Integration Services, rather than in the RDBMS. These virtual tables, which behave as standard RDBMS views, can be used anywhere regular RDBMS tables or views are used. User-defined tables enable you to create and to edit OLAP models without altering your relational schema or modifying the SQL generated by Integration Services. | |
(1) In Essbase, a process of checking a rules file against the outline to make sure the rules file is valid. (2) In Essbase Integration Services, a process of checking the OLAP model and metaoutline. | |
In relational databases, logical table created by combining columns from one or more tables. A view can contain metadata and formatting information to query an OLAP data source. | |
See user-defined tables. | |
See user-defined tables. | |
The ability for a retrieval client, such as a spreadsheet, to update a database value. | |
In Essbase Integration Services, a function that enables importing data into and exporting data from an OLAP Metadata Catalog in Extended Markup Language (XML) file format. Both OLAP models and metaoutlines can be saved as XML files and imported into other OLAP Metadata Catalogs. |