Say Goodbye to Manual SQL Optimization

So, How Can We Use Integrated Methods to Quickly and Accurately Locate Problems?

  • T1 is too late. Exception discovery and response are not in time. When exceptions are found, a large number of issues may be accumulated and cause fault risks.
  • The interval between T1 and T2 is too long, which greatly affects the user experience and dramatically increases fault risks.
  • How do we implement continuous optimization to detect and mitigate issues promptly to prevent a large number of problems from being accumulated and ensure that database instances always run stably and optimally?
  • How can we shorten the processing duration to minimize the impact and use integrated methods to ensure database instance stability and address both symptoms and root causes?

The Solution

1. Architecture

  • Exception events: Exception events trigger automatic SQL optimization and are centrally managed by the DAS event center. Exception events result from real-time exception detection, offline analysis, workload detection, and the alerting system.
  • Diagnosis: After receiving an exception event from the event center, the automatic SQL optimization service preliminarily checks the instance, sends a diagnosis request to the diagnosis engine, and processes the diagnosis result, which can be one or more recommendations. After evaluating the effectiveness, the automatic SQL optimization service generates and sends new optimization events to the event center to trigger the next optimization process.
  • Recommendation push: You can enter the DAS “autonomy center”, determine whether to accept the optimization recommendations if the full autonomy mode is disabled, and trigger the next automatic optimization process.
  • Change release: The DAS automatically selects an O&M window period, delivers the change command, and confirms the execution result.
  • Effect tracking and assessment: After the optimization recommendations take effect, the decision engine will start a tracking task to track the performance of optimized and related SQL queries. If the performance deteriorates, the optimization is automatically rolled back. Typically, if rollback is not performed 24 hours after the tracking, the optimization benefit is calculated.

2. Issue Discovery

  • Timed triggering
  • Triggered when the performance of some SQL queries deteriorates
  • Triggered when the instance workload changes

3. Diagnosis Capability

4. Secure Changes

Tested Over Time

Where Can I Find It?

Original Source:



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Alibaba Cloud

Alibaba Cloud

Follow me to keep abreast with the latest technology news, industry insights, and developer trends. Alibaba Cloud website: