ABSTRACT
Most Essbase developers will, sooner or later, be placed in the uncomfortable position of being asked to vouch for the performance of a so-called system that exists only as a quick prototype-or perhaps even just as notes scrawled on a whiteboard. Alternatively, he or she may be asked to start writing and optimizing calculation scripts when the IT department announces that the anticipated data feeds are going to be delayed another couple of months. Or perhaps the business users want to add three more dimensions to an existing system averaging 500 concurrent users and would like some reassurance that retrieval times will not skyrocket when the changes are dropped into production.
