Database Reference
In-Depth Information
Data Source
SQL Interface
ODBC
Essbase
Studio
Essbase
Figure 3.42
Essbase, Studio, and Data Source connections.
Figure 3.43
Dynamic ODBC connection string.
3.7.3 Considering XOLAP
While Studio provides a breadth of capabilities for modeling and deploying Essbase
cubes, the majority of those features can be handled by other build methods. The SQL
interface and the Data Prep Editor can handle SQL and text file modeling. Essbase
Integration Services can create and deploy drill-through reports (and you also can cre-
ate drill-through reports via maxL in recent incarnations of Essbase). The one capability
where you must use Essbase Studio is in creating and deploying an xoLAP model.
xoLAP is simply leveraging Essbase for metadata navigation and the oLAP ad hoc
experience while generating dynamic SQL back to the data source to bring back the
numbers; in short, it is the Essbase version of roLAP.
xoLAP models are ASo cubes modeled into Studio and deployed with a specific set
of options and restrictions (more on these in a moment). The value in xoLAP models is
in three main areas:
1. Latency: There zero latency between changes in the data source and the values
shown in Essbase. If the source data systems change, you see those results as
soon as you refresh your report.
2. navigation: By leveraging Essbase, you still have the oLAP navigation capa-
bilities (zoom-in, zoom-out, keep only, etc.), and you have access to the data
through all Essbase reporting front ends and APIs.
