2015 Jun 15 7:01 PM
I´m analysing the ATC report and have a doubt about the Check Message: "DB Operation SELECT for ... found."
The code is:
" SELECT <columnA> <columnB> FROM <table>
INTO CORRESPONDING FIELDS OF TABLE <ti_table>
FOR ALL ENTRIES IN <another_ti_table>
WHERE <where clause>."
Whats the problem with code above? Why ATC marks it as a problem?
Thanks!
2015 Jun 16 8:59 AM
Hi Fernanado,
I assume you executed the global inspection PERFORMANCE_DB on the coding, right? In my system, this is classified as a WARNING, rather than an ERROR, but that might differ in your system. I been asking that question myself, when I first saw that ATC result.
To my understanding, the message for that test using the variant PERFORMANCE_DB itself is of minor importance. The inspection is important for later usage and analysis of coding with the transaction SWLT (the SQL Performance Tuning Worklist). The inspection searches for DB operations in your coding which is later needed for SWLT to get the source code position of the DB operations.
More information on SWLT see SQL Performance Tuning Worklist - SQL Performance Monitoring - SAP Library.
Best,
Jasmin
2015 Jun 16 8:59 AM
Hi Fernanado,
I assume you executed the global inspection PERFORMANCE_DB on the coding, right? In my system, this is classified as a WARNING, rather than an ERROR, but that might differ in your system. I been asking that question myself, when I first saw that ATC result.
To my understanding, the message for that test using the variant PERFORMANCE_DB itself is of minor importance. The inspection is important for later usage and analysis of coding with the transaction SWLT (the SQL Performance Tuning Worklist). The inspection searches for DB operations in your coding which is later needed for SWLT to get the source code position of the DB operations.
More information on SWLT see SQL Performance Tuning Worklist - SQL Performance Monitoring - SAP Library.
Best,
Jasmin
2015 Jun 16 12:16 PM
This could help:
http://scn.sap.com/thread/1174072
I will take the message as it needs more attention(prone to performance problem) rather than there is a problem with that statement.
2024 Aug 07 12:30 PM
Hi jasmin_gruschke,
is DB Operation OPEN/CLOSE/FETCH CURSOR found also a part of this check, can we ignore this error with a pseudo comment.
Thanks & Regards,
JN
2016 Jun 08 9:04 AM
Hi,
We are also getting this message during ATC check using PERFORMANCE_DB variant. Only one select in the program and its giving "DB Operation SELECT for Found".
SELECT SINGLE <fld1> FROM <TAB1> INTO <Val1> WHERE PARMS = <Value>.
I know "Search DB Operations" check is selected in PERFORMANCE_DB and it is generating message during ATC check.
Help provided on this check is not adequate to understand. I want to know - What type of coding raise this error and how we can eliminate this message from coming in ATC check.
ATC check is also raising messages for DELELE, INSERT & MODIFY.
Thanks & Regards,
Rajesh
2016 Jun 08 11:22 AM
Hi,
Try Below Code.
The code is:
Note: <ti_Table> must have two colums with ColumnA, ColumnB
" SELECT <columnA> <columnB> FROM <table>
INTO TABLE <ti_table>
FOR ALL ENTRIES IN <another_ti_table>
WHERE <where clause>."
Now Check with ATC.
Actually Into Corresponding fields give performance issue.
I hope this answer is helpful to you,
Thanks in advance.
Regards,
Surendra.
2016 Jun 30 10:03 AM
Hi,
What I have found is - If we have selected "Search DB Operations" in our variants. It will list down all the DB related Queries - SELECT, DELETE, UPDATE, INSERT in program. Prime purpose of selecting this option to get the list of DB interaction from program.
Thanks & Regards,
Rajesh