The great migration debate: Essbase to Analysis Services
Talks about migration option from Hyperion's Essbase to Microsoft's Analysis Services using ExoLogic package called CubePort .
There may be multiple political/managerial reasons behind a decision to move from Hyperion's Essbase to Microsoft's Analysis Services – not least of which might be the recent purchase of Hyperion by Oracle.
Whatever the reason, from a developer's viewpoint, moving a set of multi-dimensional databases from one engine to another is non-trivial. What are your options?
At the risk of teaching my grandmother to suck eggs, moving a cube isn't really about the data, it's about the meta data. The raw data is typically held in a relational database somewhere and the cube is refreshed from that data source every night.
Tags: essbase