WebI reports based on BW query too slow

[Former Member]

Hi,

We created WebI reports based on BW query (DSO based). When we run those reports from InfoView, it takes forever and eventually times out. The SM50 of the BW system should that it is trying to insert records to the "Template of Query Processing" tables - I believe these are temporary SID tables in BW.

Any help is highly appreciated.

Thanks.

[Former Member]

See this documents

[http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/006b1374-8f91-2d10-fe9c-f9fa12e2f595]

[http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/008d15dc-f76c-2b10-968a-fafe5a121129]

SAP BusinessObjects Web Intelligence XI 3.x and SAP NetWeaver Business Warehouse Implementation Best Practices

[Former Member]

Hi PrabuG

There are many notes to the BW system who helping with the performance. Below is the newest one.

The best performance is, if you are making the calculations in a transformation, so the calculations are made in the dataload.

Regards,

Rikke

General performance (OSS note: 1142664):

SP8:

1489375 - MDX: High memory consumption with Descendants / Leaves

1481568 - MDX: YTD, calculated members and many dimensions

1479836 - MDX: Generate - Too many hierarchy levels are read

SP7:

1454543 - MDX: Optimized data query for IIF statement

1450366 - MDX: High memory consumption with Intersect(), Crossjoin()

1448691 - MDX: Performance of set

1448445 - MDX: Performance improvement of EXCEPT() function

1446437 - MDX:Increased memory consumption for op in calculated member

1437074 - MDX: Optimization of IIF statement for property values

1430427 - MDX: Increased memory consumption for calculated members

1426394 - MDX:Increased memory consumption with YTD calculated members

1425854 - MDX:Increased memory consumption w/ calculated member tuple

1410242 - MDX: Performance of LAG() and LEAD()functions

Incorrect data (OSS note: 1156101):

SP8:

1499233 - MDX:bXML flattening, unbalanced hierarchy, empty columns

1485648 - MDX: bXML flattening and hierarchies and displaced columns

1478973 - MDX: Missing data for calculated member

1464823 - MDX: Too much data if SUBSELECTs are used

SP7:

1461146 - MDX: Incorrect data when the query result is very large

1459126 - MDX: Incorrect values for COUNT( [,EXCLUDEEMPTY)

1458159 - MDX: Blank cells when using calculated members

1457856 - MDX: Missing values for calculated members

1455729 - MDX: No data for StrToMember()

1453365 - MDX: Missing values for structure elements & DefaultMember

1446750 - OLE DB for OLAP: Restriction on MEMBER_CAPTION and [ALL]

1443383 - MDX: No data for calculated members

1438935 - MDX: No data during LastPeriods()

1435844 - MDX:Wrong no. decimal places for basXML flattening interface

1435289 - MDX: Sorting incorrect for Hierarchize()

1435193 - MDX: Incorrect data due to optimized IIF statement

1432162 - MDX: Flattening problems when using hierarchies

1430003 - MDX: Incorrect data with Filter() w/ more than one dimension

1420169 - MDX: bXML flattening: Subsequent note

1415622 - MDX: Empty cells in calculated measure and structure

1412732 - MDX: Ascendants function does not return member

1407607 - MDX: IS operator does not recognize equality

1404328 - MDX: bXML flattening and PROPERTIES: Columns overwritten

[Former Member]

Hi, did you update the BW system? SAP's best practice document lists many notes which should be implemented, mainly performance related.

Also, which BO version are you on?

Third, I've had good results by implementing optimized synthax as described in the best practices document and by specifying the aggregation function for measures instead of leaving the default "database delegated" (which is buggy BTW, see SAP notes)

[Former Member]

Pabloj, thanks for your response. Yes, the query is based on DSO and in BEx it takes few secconds only. We are using BO XI3.1 SP3.

Where can I get the best practice document? Yes, we are using aggregation function instead of database delegated.

Thanks

[Former Member]

Hi

Is the query based on a DSO? What happening if you run the query in BEX?

Regards,

Rikke