Query performance for WEBI on top of BEx

Hello Everyone,
Is there a way to get the time taken by a webi query execution on the BO side and in the BW side? Is this stat stored some where?
Also, what is the best approach to take for comparing performance between the original bex query and the WEBI on top of the Bex?
Thanks for your help.
Aashish

Hi,
i posted some links for the same Question here:
Poor query performance in WebI on top of BEx queries
Maybe those can help you.
Regards
-Seb.

Similar Messages

Poor query performance in WebI on top of BEx queries

Hello,
We are using Web Inteliigence i BO 3.1 (SP0) to report on BEx queries (BW 7.0).
We experience however that reporting is much quicker for the same set of data when using BEx Analyzer than when using WebI. In BEx it is acceptable, but in WebI it's not.
How can we optimize the performance in this scenario? What tricks are there?
The amount of data is not huge (max 500 000 records in the cube)
BR,
Fredrik

Hi,
Dennis is right. But if you need to upgrade (and you do) than maybe going to the latest SP is better. It is SP4. With SP3 the WebI Option "Query Striping" has been introduced which brings Performance as well.
Also check
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d0bf4691-cdce-2d10-45ba-d1ff39408eb4
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/109b7d63-7cab-2d10-2fbc-be5c61dcf110
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/006b1374-8f91-2d10-fe9c-f9fa12e2f595
Regards
-Seb.

Webi on top of Bex query, maximum of fields 50 limit

Hi there,
I'm creating the Webi Report on top the Bex Query that has 50 characteristics in the row area and around 10 characteristics in Free Characteristics area. (Bex query can't have more than 50 in the Row Area)
When I create the WEbi report, it limits the output to the same 50 characteristics, it means that even though I have 10 more characteristics available from the Free Characteristics Area and I can't add them to the Webi Report.
I'm new to Webi and I didn't know about this limitation of number of fields can be added. Is there a workaround for this case?
Is 50 fields really a limit for Webi Report or am I doing something wrong here?
Thanks!

Hi,
Much like BEx, with WebI it is recommended to not have more than 50 dimensions selected into a single OLAP query, otherwise performance will degrade.
I have customer who try to put 80-200 objects into webi query panel and get angry when they can't...
However, this is a silly thing to do. For example, how many people can read tables with 80 columns?
It usually mean that the business requirements aren't being focused enough, and that reports are trying to answer too many flexible u2018ad hocu2019 purposes.
To conclude, it's an u201Cirrelevant testu201D because WebI isnu2019t a u2018data dumpu2019 tool. you should perhaps use a genuine ETL to extract records for hundreds of objects
Regards,
H

Allow the external access to the query massage for WEBI in BO 4.0 ,

Hi ,
I created the BEX query and in query properties I checked " Allow External access to this query" and saved the query
but this check box option " Allow External access to this query" is not saving .
is there any note need to be implimented for this problem.
I created the the connection using the information design tool.
I'm trying to create the Webi using BICS connection form BEX query through Web intellengence rich client
it is giving the message like "it is not possible to use this Bex query as source for Web intellengence reports. Ask your administrator to edit this query so that it can be used by
web intellengence and enable the query propery" Allow External access to this query.
we are using BI - 7.35 support pack 4 and BO - 4.0 SP2
Did any one has faced this issue, Could you please send your comments
Regards
JV
Edited by: Jennie Juvvanapudi on Oct 13, 2011 3:43 AM

Upgrade your SAP GUI to 720 and there will be a updated patch at service market place for GUI 720 which will resolve this issue.
When we faced same issue we had upgraded and our system currently shows
SAP GUI Release: 720 Final Release
File Version: 7200.3.7.1066
Build: 1257409
Patch Level: 7
Thanks,
Suresh

Query Performance for OLE DB OLAP Reporting

Hi Experts,
what are the advantages of enhancing query performance by
A) building Aggregates or
B) using Information Broadcaster Query Precalculation?
Since the settings in Information Broadcaster could be done by any user - will the precalculated version be used only for this user or for all users exeucting the query?
Are these settings also used if the query is executed via a 3rd party Frontend tool?
Thanks,
Angie

Hi Angie,
Which is the third party tool that's accessing the query? Is it BO? If so there's a lot of information available.

Behavior of BEx Query Attributes for webi on OLAP universe: Including 1 attr to Query!

My webi report is based on an OLAP universe (.unv) which is based on a BEx Query. I need an attribute field from an info object. But when I include that attribute in my BEx query in free characteristics pane…… Every single attribute in that info object comes over to the universe.
Is this the expected behavior?
How can I ensure only the attribute wanted comes over and not all the attributes of the info-object.
I am using BO 4.0SP4.

Attribute level restriction of an InfoObject is not possible in BEX Query and the same reflects in the Universe.
You can use attributes of an infoObject which you wanted on WEBI Report Level.
---Raji. S

Poor Performance with Webi on top of BW - Large Navigational Attributes

We have recently developed a reporting model based on having a BW cube of approx 20 million records. This has 2 very large line item dimensions (one 14 million records, on 6 million records) that both have navigational attributes stored against them.
We need the design to be like this because the attributes change monthly and we do not wish to do a complete drop and reload of cube data each month (this takes 10-12 hours).
When we build a Universe on top of the cube and try Webi reporting the performance is dreadful - many reports time out completely. This happens whether or not the large line item dimensions are selected in the query. The BW query is very simple just 2 key figures and approx 30 Navigational Attributes as default values. No filters are applied.
For example a query that just contains Calander Year and one key figure either times out after 10 minutes or fails.
Our source of the data is Oracle tables and the same query runs in 2 1/2 minutes and the query runs in RSRT in approx 5 minutes with no problems so it is definately a problem with BOBJ to MDX to BW.
We are on BW7.01 SP5 and XI3.1 SP2. SAP have recommend going to SP3 and using query stripping to help with this but I doubt if this will work.
We have tried building aggregates, splitting into yearly cubes etc but nothing seems to help.
My question is do the large navigational attributes mean Webi simply can't cope with this?
Thanks

Thanks for the suggestions.
Although this did not directly help I've now found a solution.
We had a calculated key figure in the query that doing a count of records on a huge navigational attribute. This was causing all queries to run very slowly (even if the key figure wasn't selected in Webi).
Removing it solved the problem. Will have to find another way to do the count key figure.
Thanks

CAML query performance for large lists

I have a list with more than 10000 items. I am retrieving the items and displaying it in a RAD Grid on my page using CAML query. While retrieving the items, around 1000 records are retrieved due to filter. I have enabled paging in my grid and PageSize is
set to 25. I have noticed that the load time of my page is very slow as it retrieves all the 1000 records at once.
Is it possible to retrieve just 25 records for the first page on load. On click on the Next button or Page number it should retrieve the next set of 25 records for that particular page.
I want to know if there is any way to link CAMl query paging with RAD grid paging
Any code example would be greatly helpful.

Hi,
For pagination in SPListItem use the SPQuery.ListItemCollectionPosition property.
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spquery.listitemcollectionposition(v=office.15).aspx
check the usefull urls
http://omourad.blogspot.in/2009/07/paging-with-listitemcollectionposition.html
http://www.anmolrehan-sharepointconsultant.com/2011/10/client-object-model-access-large-lists.html
Anil

Query Performance Issues on a cube sized 64GB.

Hi,
We have a non-time based cube whose size is 64 GB . Effectively, I can't use time dimension for partitioning. The transaction table has ~ 850 million records. We have 20+ dimensions among which 2 of the dimensions have 50 million records.
I have equally distributed the fact table records among 60 partitions. Each partition size is around 900 MB.
The processing of the cube is not an issue as it completes in 3.5 hours. The issue is with the query performance of the cube.
When an MDX query is submitted, unfortunately, in majority of the cases the storage engine has to scan all the partitions (as our cube is not time dependent and we can't find a suitable dimension that will fit the bill to partition measure group based
on it.)
I'm aware of the cache warming and usage based aggregation(UBO) techniques.
However, the cube is available for users to perform adhoc queries and hence the benefits of cache warming and UBO may cease to contribute to the performance gain as there is a high probability that each user may look at the data from different perspectives
(especially when we have 20 + dimensions) as day(s) progress.
Also, we have 15 + average calculations (calculated measures) in the cube. So, the storage engine sends all the granular data that the formula engine might have requested (could be millions of rows) and then perform the average calculation.
A look at the profiler suggested that considerable amount of time has been spent by storage engine to gather the records (from 60 partitions).
FYI - Our server has RAM 32 GB and 8 cores and it is exclusive to Analysis Services.
I would appreciate comments from anyone who has worked on a large cube that is not time dependent and the steps they took to improve the adhoc query performance for the users.
Thanks
CoolP

Hello CoolP,
Here is a good articles regarding how to tuning query performance in SSAS, please see:
Analysis Services Query Performance Top 10 Best Practices:
http://technet.microsoft.com/en-us/library/cc966527.aspx
Hope you can find some helpful clues to tuning your SSAS Server query performance. Moreover, there are two ways to improve the query response time for an increasing number of end-users:
Adding more power to the existing server (scale up)
Distributing the load among several small servers (scale out)
For detail information, please see:
http://technet.microsoft.com/en-us/library/cc966449.aspx
Regards,
Elvis Long
TechNet Community Support

RRMX for web report?

Hi,
Just busy defining authorizations for web reports based on BEx queries. In the role is the S_TCODE=RRMX REALLY needed? And if so does that entail that the users can use BEx query designer as well?
Thnx for thinking.

Thnx.
Do you refer to the "change local/global definition" in "excel" via the BEx query designer? Because that is the functionality that I would like to restrict, web access only.
By different "auth objects" you refer to the S_RS_COMP etc?
Thnx in advance.

Query performance on Multiprovider(Remote Cube)

Hi All,
I have to increase the query performance for a report which built on Multi provider.
This multiprovide designed from several remote cubes,but for this report data will bring through one remote cube from R/3.
In filter i had one remote cube, which bring data from R/3.
Now in ST03 the stats are like
%init Time - 0, %DB time - 0, %OLAP time - 16.67, %Front end - 83.33.
Now i have to improve the %Front end lapsed time.
Could you please guide me.
Thanks
Srinivas

Hi Srinivas,
Please see this document
https://websmp105.sap-ag.de/~sapidb/011000358700001394912002
And this Discussion Thread
Re: Deactivate Hierarchy symbols in excel
See whether this is helpful in case of Remote Cubes.
Thanks
CK

Steps to Improve Query Performance

Hi All,
I have a request from User to improve the Query performance for few of the sales reports. Please let me know the different steps I need to perform to improve it.
The data is coming from R/3 and the query is on a Multicube modeled upon three Cubes.
It takes way lot of time to open and refresh the report an further execute. The data available is not really huge but still it is taking time.
Tell me what are the areas that i need to check to understand the issue and how should o progress to improve the performance.
It would be great help if you can help me with as much details as possible.
Thanks in advance
Pavan

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3f66ba90-0201-0010-ac8d-b61d8fd9abe9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c8c4d794-0501-0010-a693-918a17e663cc
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/064fed90-0201-0010-13ae-b16fa4dab695

Performance - Crystal on top of BEx against Cube - Universe - WebI

Hello All,
We are using Crystal Reports built on top of BEx queries. The BEx queries use aggregates and we have a good performance. My question is
Can we create an Universe on top of Info Cube and build WebI and expect the same performance as we get now? I have not seen any documentation about the BIA or Aggregates are being used by Buiness Objects yet. Could anyone throw some light at this?
Thanks,
Arthur.

Hi,
you would build a Universe on top of the BW query and the query would still use the aggregates from your BW system like it was doing that before.
aggregates and the usage of BIA are transparent to the BusinessObjects tools.
Ingo

WebIntelligence report on top of bex Query in BI4.0 (SP2)

Dear experts,
I'm working on webi report on top of bex Query in BI4.0 (SP2). I would like to know your opinions about some points I have noticed.
A - I need to drill throught a hierarchy which contains several millions of members.
Is there a possibility in my report drilling down to one member without selecting all members of the hierarchy in the query panel ?
B - I cannot put a dimension with hierarchy both in the result pane and in the filter pane, although it is possible for any other dimension without hierarchy.
Is there any special trick to achieve this or is a bug??
C - I cannot sort variables defined in my bex query, but they don't appear in the window to sort prompts.
Do you know how to solve this issue ?
D - I noticed all keys and description of dimensions appear with the same label "key" and "text". SO it is very confusing for the user to understand what key or text means (if a key if the customer key or the company code key).
Any idea to have a more explicit label for BW characteristics?
Regards.
CL.

Hi,
I do not have access to a BW system to test this, but i have something on three of your questions...
A) drilling without getting all the lower members. I would look to query drill, this means a drill action in the report will go to the database to fetch the level (and only for the selected member, a drill down).
The only thing I'm not sure about is if the BEx hierarchy is seen as drill hierarchy by that option too.
If you'd ask me it really should.
C) this is an old problem, but I know it is bugging more people, because the same is true for universe based prompts. They also cannot be 'arranged'. Since the Bex query is the 'universe', ordering that has been set in the 'universe' is the only chance you have.
Like with the universe you could use prefixes to separate them from the query defined prompts (based on an alphabetic sort of the prompt message). I'd say this is a good one for the idea place...
D) also an old (very old actually) problem. Some will want to keep the text short and simple. The prefixing will tell which key it is. Some will prefer unique names, so no prefix is needed. The same was true for universe designers. Now since there is no universe, if you do not agree with the 'designer' you're out of luck no way to change it.
Hope this helps,
Marianne

Webi report on OLAP Bex query - Cost element Hierarchy not working Drill down

Hello,
We have a BO report on Bex query, Not on universe, we have a Hierarchy for Cost Element Group, and we are expecting the Drill down functionality for that in BO report, but it does not.
Webi report on OLAP Bex query - Cost element Hierarchy not working Drill down
Any pointers how to do it please
Thanks
Krishna

Hi,
WebI reports on BEx source don't use same Drill feature as other sources, it's replaced by expland/collapse of hierarchy nodes (documented in WebI user guide in § "24.1 Drill defined"). This means you have to create query which selects all hierarchy sub-tree you plan on exploring later in report, otherwise if no data is available under a node there will be no '+/-' sign to visit this part of tree.
You could try first to select "All members" from hierarchy in QueryPanel and see if behavior in report suits your needs. Then you should restrict hierarchy member selection to what's really needed to avoid performance issues.
Regards,
Loic

Query performance for WEBI on top of BEx

Similar Messages

Maybe you are looking for