Database Reference
In-Depth Information
Figure 3.7 Sample mini-schema.
on this topic later in the chapter; however, in respect to data I often recommend the
modeling of dimensionality with Studio, but loading data directly with the Data Prep
Editor. to take that sentiment one step farther, I often recommend that you model your
dimensionality with Studio, but perform the dimension build processes manually lever-
aging the Load rules Studio generates.
At its core, Essbase Studio tool is a graphical Load rule generator whose output need
not be a cube. In fact, there is an overt option to simply generate Load rules, which can
then be used in standard batch process or leveraged manually to build the dimensional-
ity and load the data as you see fit.
If you do end up creating a mini-schema, there are a number of options to consider
when selecting and joining tables within the mini-schema. In general, you should only
add those tables to the mini-schema that are necessary for the following purposes:
•  to derive the required hierarchies (either cross-table or within table)
•  to load data from the primary or alternate fact table (assuming data is being
loaded via Studio)
Adding nonjoined tables simply clutters the user interface. Furthermore, adding
additional (optional) tables to the join process unnecessarily complicates the SQL issued
by Studio.
3.4.1 Mini-Schema versus View/Tables
From a prototype perspective, leveraging the mini-schema to handle to cross-table
dimension builds and complex data loads is fine. however, for longer-term scalability, it
is preferable to build tables or views directly in the relational source and minimize the
required joins and cross-table builds within the mini-schema. Placing the tables or views
directly in the source allows Studio to go after a single database object per dimension.
This has advantages from two perspectives. First, the SQL issued for dimension
builds is far less complex. Second, the relational DBAs (database administrators) can
write more efficient SQL to define the table or view. While you have the option of writing
Search WWH ::




Custom Search