Performance, security and the right information are three main concerns that arise when downloading and creating reports from SAP. You may often end up with sub-optimal queries that either take too long or are worse scenarios – negatively impacting your SAP system. Thus, the author of an SAP query has a big task at hand. The external contributing factors like network capacity or the inherent vagaries of the SAP system make this task even more difficult. The good news is that you don’t need be a technical expert to properly handle these situations. Winshuttle Query is the go-to platform for companies and analysts that want to implement a non-technical solution that makes SAP more accessible. Check out the tips below on how you can leverage features provided within Winshuttle Query to create better performing queries.
Top 5 features that will improve queries
1. AQT or Adaptive Query Throttling ensures that your SAP system is not impacted by large queries. In some cases, you might find that queries without AQT take much less time. How do you decide on what mode to use?
AQT runs in controlled smaller calls to the database server, so it can execute beyond the dialog (foreground) process timeout limit of the SAP server, allowing larger queries to run. It ensures that for the duration of its run, it will consume partial server resources and prevent the risk of making the SAP system inaccessible.
Therefore, if you have larger queries, it is better to run with AQT even if it takes a little longer to execute. Smaller queries will run faster without AQT.
2. SAP background process is another tweak that can be applied to queries to avoid impacting your SAP system. It is different than AQT since it does not consume any foreground processes. It is recommended for queries with large data sets.
3. Use chunking when the threshold of result writing is achieved through limited network channel or limited data read/write capacity. Chunking, like SAP background process, is also recommended for larger data sets. However, it achieves better results when network bandwidth or database read capacity is an issue, not the number of free dialog processes.
4. Including join fields as selection criteria will greatly impact the performance of queries. This difference is profound when you run queries on an SAP system without the Winshuttle Function Module. See the graph above.
5. Joins should be created in the following order:
- By Field types: Primary key fields – Indexed fields – Non Indexed fields (highly degraded performance)
- By Type of join: Inner Join – Outer Join
- By Table types: Transparent Tables – View – Cluster and Pool Tables
Questions or comments about this article?
Tweet @Winshuttle to continue the conversation!