Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago

XMLA with MDX issues (timeouts and process multiplication)

Hello    I am trying to retrieve data from Essbase to PBI. For this i am using the Harry Gates method (thanks to him! :) ) When the Essbase has been newly started, i can retrieve my data very fas...
Need Help
Anonymous's avatar
Anonymous
Not applicable
8 years ago

HI Anonymous,

 

I think this issue is more related to Essbase settings, please double check on its settings to confirm any limit on it.(for e.g. request amount, request interval, ip address limit...)

 

Regards,

Xiaoxin Sheng

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Hi!
We investigated the Essbase side. We could not find anything wrong.

It looks like that Power BI was bombing our Essbase server with dozen of requests.

My Power BI software is up-to-date.

BR, G.

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    HI Anonymous,

     

    I'd like to suggest you to use fiddler trace your httprequest to confirm where caused the issue.

    Fiddler - Free Web Debugging Proxy - Telerik

     

    Regards,

    Xiaoxin Sheng

  • harrygates's avatar
    harrygates
    Frequent Visitor
    8 years ago

    Hi Ghuiles,

     

    Your MDX is suboptimal, to put it mildly, from an Essbase perspective. Try something like the following:

    SELECT NON EMPTY ( {[Local Currency]})
    ON COLUMNS,
    NON EMPTY (

    crossjoin(DESCENDANTS([Accounts],
    crossjoin(leaves([Total Cost Center]),[GAC 32014].LEVEL)
    ))
    on rows from [Group.HL]

    where ([Y2016],[Actual],[Local Reporting],[Jan],[Germany],[Total Customers],[Total Service Type])

     

    You should also take a look at the Power BI connector for Essbase that I recently wrote: https://casabasesoftware.com/products/casabase-power-bi-connector-for-essbase/

     

    Regards,

    Harry

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      Hi!

      Thanks for the improvement :)

      I will check within my company if we can / shall use the connector.

      Best regards. G

      • Anonymous's avatar
        Anonymous
        Not applicable
        8 years ago

        Hi!

        In the meantime our Essbase advisor looked at what happened. According to him the MDX is not an issue. The issue is coming from the multitude of simultaneous queries. This can be done because in PBI either the queries are not stopped after the results are back, and because PBI generates by itself several queries rapidly for whatever reason. Note: i was the only PBI user on this server.

        Does anybody has any clue on how PBI is processing such XMLA queries? Is there a way to adapt it?

        Best regards

        G