Shulou(Shulou.com)05/31 Report--

Most people do not understand the knowledge points of this article "how to solve the SQL judgment and acquisition problem", so the editor summarizes the following content, detailed content, clear steps, and has a certain reference value. I hope you can get something after reading this article. Let's take a look at this "SQL judgment and access problem solving" article.

Determine the problem SQL

1. Whether there is a problem with SQL can be judged by two representations: the system-level representation and the SQL statement representation.

System level representation

Serious CPU consumption

IO waiting is serious

The page response time is too long.

Errors such as timeout occurred in the applied log

You can use the sar command, the top command to view the current system status. You can also observe the status of the system through monitoring tools such as Prometheus and Grafana.

SQL statement representation

Tedious

The execution time is too long

Get data from a full table scan

The rows and cost in the implementation plan are very large.

Long SQL is easy to understand, a SQL too long reading will certainly be poor, and the frequency of problems will certainly be higher.

Get question SQL

Different databases have different access methods.

2. The current slow query SQL acquisition tools of mainstream databases: MySQL, Oracle, Dameng database.

The above is about the content of this article on "how to solve the problem of SQL judgment and acquisition". I believe we all have a certain understanding. I hope the content shared by the editor will be helpful to you. If you want to know more related knowledge, please pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.