Some ideas for tracking top SQL recently

1. in the list of top SQL statements, the first priority is the number of disk reads executed each time. The larger the number, the worse it is, but it cannot be absolute, pay attention to the number of processed rows. If the number of rows is large, the number of disk reads is normal. That is to say, we need to care about the number of records read each time on the disk.

2. note that syntax analysis calls this indicator. When a large number of top SQL statements use statements with syntax analysis calling 1, the following two problems are described:. your statement may have been executed only once; B. your statement cannot be re-resolved. It may be because your statement does not use the bound variable or repeated parsing. your library cache is relatively small, causing frequent exchanges of parsed SQL statements.

3. Based on these situations, we found that SQL problems are mainly caused by the absence of Bound variables.