首页 > Linux操作系统 > Linux操作系统 > 关于BW Query Performance 的一些问答(1)

关于BW Query Performance 的一些问答(1)

原创 Linux操作系统 作者:leniz 时间:2009-09-25 16:47:26 0 删除 编辑

1. What kind of tools are available to monitor the overall Query Performance?

o BW Statistics
o BW Workload Analysis in ST03N (Use Export Mode!)
o Content of Table RSDDSTAT

2. Do I have to do something to enable such tools?

o Yes, you need to turn on the BW Statistics:
  RSA1, choose Tools -> BW statistics for InfoCubes
  (Choose OLAP and WHM for your relevant Cubes)

3. What kind of tools are available to analyse a specific query in detail?

o Transaction RSRT
o Transaction RSRTRACE

4.  Do I have a overall query performance problem?

o Use ST03N -> BW System load values to recognize the problem. Use the
  number given in table 'Reporting - InfoCubes:Share of total time (s)'
  to check if one of the columns %OLAP, %DB, %Frontend shows a high 
  number in all InfoCubes.
o You need to run ST03N in expert mode to get these values

5. What can I do if the database proportion is high for all queries?

o If the database statistic strategy is set up properly for your DB platform 
  (above all for the BW specific tables)
o If database parameter set up accords with SAP Notes and SAP Services (EarlyWatch)
o If Buffers, I/O, CPU, memory on the database server are exhausted?
o If Cube compression is used regularly
o If Database partitioning is used (not available on all DB platforms)

6. What can I do if the OLAP proportion is high for all queries?

o If the CPUs on the application server are exhausted
o If the SAP R/3 memory set up is done properly (use TX ST02 to find
o If the read mode of the queries is unfavourable (RSRREPDIR, RSDDSTAT,
  Customizing default)

7. What can I do if the client proportion is high for all queries?

o Check whether most of your clients are connected via a WAN Connection and the amount 
  of data which is transferred is rather high.

8. Where can I get specific runtime information for one query?

o Again you can use ST03N -> BW System Load
o Depending on the time frame. you select, you get historical data or
  current data.
o To get to a specific query you need to drill down using the InfoCube
o Use Aggregation Query to get more runtime information about a
  single query. Use tab All data to get to the details.
  (DB, OLAP, and Frontend time, plus Select/ Transferred records,
  plus number of cells and formats)

9. What kind of query performance problems can I recognize using ST03N
   values for a specific query?

(Use Details to get the runtime segments)
o High Database Runtime
o High OLAP Runtime
o High Frontend Runtime

10. What can I do if a query has a high database runtime?

o Check if an aggregate is suitable (use All data to get values
  "selected records to transferred records", a high number here would
  be an indicator for query performance improvement using an aggregate)
o Check if database statistics are update to data for the
  Cube/Aggregate, use TX RSRV output (use database check for statistics
  and indexes)
o Check if the read mode of the query is unfavourable - Recommended (H)

11. What can I do if a query has a high OLAP runtime?

o Check if a high number of Cells transferred to the OLAP (use
  "All data" to get value "No. of Cells")
o Use RSRT technical Information to check if any extra OLAP-processing
  is necessary (Stock Query, Exception Aggregation, Calc. before
  Aggregation, Virtual Char. Key Figures, Attributes in Calculated
  Key Figs, Time-dependent Currency Translation)
  together with a high number of records transferred.
o Check if a user exit Usage is involved in the OLAP runtime?
o Check if large hierarchies are used and the entry hierarchy level is
  as deep as possible. This limits the levels of the
  hierarchy that must be processed. Use SE16 on the inclusion
  tables and use the List of Value feature on the column successor
  and predecessor to see which entry level of the hierarchy is used.
- Check if a proper index on the inclusion  table exist

12. What can I do if a query has a high frontend runtime?

o Check if a very high number of cells and formattings are transferred
  to the Frontend ( use "All data" to get value "No. of Cells") which
  cause high network and frontend (processing) runtime.
o Check if frontend PC are within the recommendation (RAM, CPU Mhz)
o Check if the bandwidth for WAN connection is sufficient

来自 “ ITPUB博客 ” ,链接:,如需转载,请注明出处,否则将追究法律责任。

下一篇: 双节之后
请登录后发表评论 登录


  • 博文量
  • 访问量