Page 1 of 1

Expensive MSSQL Statement

Posted: Mon Apr 25, 2016 4:24 am
by chutney374
Hi all

I'm looking at SAP systems and noticing a number of expensive MSSQL statements running. Whilst the end user community aren't complaining of slow performance, I'm looking at area's of continual improvement possibilities. I've reviewed SAP EWA reports and all they state is to follow the recommendations below (although there are no recommendations).

When there is an expensive mssql statement, are there any guidelines anyone is aware of for addressing expensive statements?


Paul M

Re: Expensive MSSQL Statement

Posted: Thu Apr 28, 2016 7:37 am
by Zavaros

there are only few rules for expensive SQL statements:
As Basis guy you can do:
- check if an index can improve the execution plan
- check if buffering (SAP level, DB level) can help. Be aware that there are tables that should not be buffered!
- check if more memory could improve performance
- in ORACLE hardcoded statistics and profiles could make magic ... I do not know the MSSQL equivalent

As Module expert you can do:
- check if splitting processed data improves the performance
- check if the expensive statement can be redesigned. Sometimes it is a simple developer task but more often it comes from business logic...
- therefore check if the business logic can be tuned to simplify the expensive db statement.