Re: max nesting with XMLA

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

128 is a default value, but which value would you like to advise ?

Is there any more info in a tech document?

Regards, Marco

"Akshai Mirchandani [MS]" <akshaim@xxxxxxxxxxxxxxxxxxxx> wrote in message news:<uEZd8r4PFHA.2132@xxxxxxxxxxxxxxxxxxxx>...
> Its actually a property in the file datasources.xml in the ...\config folder
> of your installation. The property is called MaxRequestSize and its default
> value is 128 KB.
>
> MaxRequestSize="128"
>
> Thanks,
> Akshai
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
> Please do not send email directly to this alias. This alias is for newsgroup
> purposes only.
>
> "Marco Groeneveld" <olap@xxxxxxxx> wrote in message
> news:211f845f.0504120944.215acb32@xxxxxxxxxxxxxxxxxxxxx
> > Can you give an example of the statement to change in datasources.xml
> > for testinf default value and more?
> >
> > Never the less XMLA is still great !
> >
> > Regards, Marco
> >
> > "Akshai Mirchandani [MS]" <akshaim@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:<#HbE1KtPFHA.2468@xxxxxxxxxxxxxxxxxxxx>...
> > > Well, I actually take back what I said -- XMLA does have a limit on the
> > > request size. You can change this limit in the datasources.xml file.
> Perhaps
> > > this is what you are running into. However, I can't say that there is
> > > something special about 7 slicers in the query. XMLA SDK doesn't really
> care
> > > about the contents of the query itself...
> > >
> > > Perhaps you could trace the query generated and try to run it as a
> > > standalone query and see the result size.
> > >
> > > Thanks,
> > > Akshai
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights
> > > Please do not send email directly to this alias. This alias is for
> newsgroup
> > > purposes only.
> > >
> > > "Marco Groeneveld" <olap@xxxxxxxx> wrote in message
> > > news:211f845f.0504080628.2e232eab@xxxxxxxxxxxxxxxxxxxxx
> > > > Hi,
> > > >
> > > > I have experience with Panorama NovaView 4.5 and ReportPortal 2.0
> > > > based on XMLA. Panorama is using a cache mechanisme and supports more
> > > > data, slicers and nestings compared with ReportPortal XMLA.
> > > >
> > > > So is there a max of nestings of adding slicers in the rows in a grid
> > > > with XMLA before tha client PC stops reacting?
> > > >
> > > > You can test it adding for example 7 slicers in the rows in a grid and
> > > > see if your Client PC is still working:
> > > > http://166.122.240.100/ReportPortal/login.aspx
> > > >
> > > > I have a feeling Panorama can be used for OLAP with more data and
> > > > slicers than any other client based on XMLA?
> > > >
> > > > If you have an other opinion, please let me know.
> > > >
> > > > Regards,
> > > > Marco
> > > >
> > > >
> > > > "Akshai Mirchandani [MS]" <akshaim@xxxxxxxxxxxxxxxxxxxx> wrote in
> message
> > > news:<eFYpfC6OFHA.580@xxxxxxxxxxxxxxxxxxxx>...
> > > > > What do you mean by nesting? XMLA doesn't have any limits on queries
> (it
> > > > > simply passes the MDX on to the OLE DB for OLAP driver) -- but of
> course
> > > the
> > > > > size of the results could become large...
> > > > >
> > > > > Thanks,
> > > > > Akshai
> > > > > --
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights
> > > > > Please do not send email directly to this alias. This alias is for
> > > newsgroup
> > > > > purposes only.
> > > > >
> > > > > "Marco Groeneveld" <olap@xxxxxxxx> wrote in message
> > > > > news:211f845f.0504062304.3f16b878@xxxxxxxxxxxxxxxxxxxxx
> > > > > > Hi,
> > > > > >
> > > > > > Is there a max of nesting in XMLA 1.1 in the grid ?
> > > > > >
> > > > > > One of our customers wants more than 7 nestings and is this too
> much
> > > for
> > > > > XMLA ?
> > > > > >
> > > > > > Regards, Marco
.

Relevant Pages