Throughout this Help file and indeed in all OLATION documentation we reference the “OLATION database.” It is useful to explain further what is meant by this term: an OLATION database is a representation of data in a multidimensional-modeling context, basically for the construction of Cubes. An OLATION database stores and provides instructions to those Cubes, directing them to be organized in such a way, with certain “dimensionality” (Accounts, Regions, Months, Products, Version, etc.), as well as other characteristics that are found in more complex models: formulas and security logic come to mind.
Where does the data come from to create the OLATION database? It may derive from underlying relational database tables (and views and queries), such as those found in applications (e.g., an ERP system) that themselves are installed in a SQL Server or SAP HANA environment—just two examples of relational database management systems that OLATION will work with.
Taking SQL Server (often the basis of OLATION documentation) as the underlying data store for the construction of OLATION models: in this case we say that the OLATION database is of a type “OLATION for MS SQL Server.” In other words, the data logic for OLATION’s multidimensional modeling exists in SQL Server. That said, the data logic is not limited to what OLATION “sees” in SQL Server. Stated another way: indeed, OLATION can leverage SQL Server table (or view, or query) logic for multidimensional models, but—key point—OLATION can also create multidimensional logic (e.g., a new Dimension) that has no basis in SQL Server. OLATION can create multidimensional logic entirely on its own—and that logic can work with what has been derived from SQL Server! (Furthermore—another key point—new dimensional logic created in OLATION will be saved as relational tables, tables that can be leveraged going forward by both OLATION and the relational database system itself.)
Indeed, an entire model—no underlying SQL or other relational tables required—can be built in OLATION. And it can be saved without the need of SQL Server (or equivalent): this is what a PowerExcel database is, an OLATION database saved on its own with no “connectivity” to a relational database.
This backgrounder about “the OLATION database” should provide some context for what follows, whether the topics under this section or in the many topics that follow.
Topics under this section:
Open Existing OLATION Database