I was actually compiling all my findings of the last 4 posts as a summary post but then realized i haven't actually covered another important part of the Essbase Connectivity i.e. Essbase Security. In today's post let's look at how Essbase Security is

In the last 3 posts we saw how BI EE generates the MDX and what major factors influence the MDX generated. As a recap, there are 4 main things that we noticed. 1. BI EE generates the most optimal MDX as long as we have all the attribute or Hierarchical

Continuing along with our Essbase series, today lets look at how the various Pivoting operations that are done at the BI EE layer affect the MDX generated. We noticed that whenever we brought in an attribute column from the row-edge to the column edge, the MDX generated by BI EE

In the last post we saw how BI EE generates Essbase specific MDX while using Attribute columns for a specific case. In today's post we shall look at how the new BI EE 11g specific features like Hierarchical columns and Value-Based hierarchies affect the MDX generated. For continuation

If you had gone through my blog series for BI EE 10g and Essbase here [http://oraclebizint.wordpress.com/workshop-series/], i would have covered the different ways of controlling the BI EE MDX generated for Essbase Sources. With 11g, that too with the introduction of Hierarchical Columns and Value Based