Database Reference
In-Depth Information
methods for drill-through possibilities (maxL, ErPi, and EIS, for instance). A snow-
flake or star schema can be easily accessed using Load rules (and the SQL interface),
and a new deployment may be better served with Load rules and oDI automation. The
most compelling reason on paper is the replacement of EIS. oracle has publically stated
that the EIS component is being sunsetted in favor of Studio.
I use and recommend Studio because its flexibility and power gives it the ability to
bridge all data gaps. When you are trying to get things cleaned up, you often have to
compromise. you clean some rooms because you have time for it. In other places, you
focus on the known issues. What Studio provides is a tool that allows you to quickly
and iteratively transform a completely unsuitable data source to one that is just clean
enough. to repeat a statement from earlier in the chapter:
Understanding a client's data
is about iteration. You may never fully understand all the nuances or complexities until
you hit roadblocks in the build process
.
Studio is that ideal component for cutting through the clutter so you can quickly
provide value to the user community. to take that a step farther, from my perspective,
Essbase Studio is key to prototyping in Essbase. If for no other reason, that powerful and
flexible prototyping functionality is why Studio should be included in your development
process.
