This document mainly introduces the use scenario of full SQL function of DAS (previously referred to as HDM).
MySQL database users normally have these three differents:
Historical problems are hard to locate.
There is a CPU 100% alarm at 3:00 a.m. in the database, but there is no slow SQL in this time period. How can we find the cause and solution of this problem?
SQL Stress Test Template is difficult to obtain.
Next week, a large-scale stress test will be carried out. DBAs can only collect SQL templates and execution frequency one by one from the business side. This method is inefficient and the correctness cannot be ensured;
Whether slow SQL should be optimised?
Not all slow SQL needs optimization at first priority level. Users urgently need to know which SQL on the database consumes the most resources. Only by optimizing these SQL can the stability of the instance be improved;
Full SQL Diagnosis can solve the above problems in a short time.