Database Autonomy Service (DAS) provides the SQL Explorer and Audit feature. If you want to monitor and manage SQL statements that are executed in database instances, you can use the SQL Explorer and Audit feature to record and analyze the execution of SQL statements. After this feature is enabled, SQL statements from database kernels, the accounts that are used to execute the SQL statements, IP addresses, and execution details are automatically recorded. This does not affect the instance performance. You can also use the traffic playback and stress testing features to check whether you need to scale up or scale out your database instance to handle workloads during peak hours.
Supported databases and regions
You can use the SQL Explorer and Audit feature only after DAS Enterprise Edition is enabled. The databases and regions that are supported vary with the versions of DAS Enterprise Edition. For more information, see the "Supported databases and regions" section of the DAS Editions and supported features topic.
Feature description
Search: This feature is used to query and export SQL statements and related information, such as the databases on which the SQL statements are executed, the status of SQL requests, and the execution duration of each SQL statement. For more information, see Search (Audit).
SQL Explorer: This feature is used to diagnose the health status of SQL statements, troubleshoot performance issues, and analyze business traffic. For more information, see SQL Explorer.
Security audit: This feature is used to automatically identify risks, such as high-risk SQL statements, SQL injection attacks, and new access sources. For more information, see Security audit.
Traffic playback and stress testing: These features are used to check whether you need to scale up or scale out your database instance to handle workloads during peak hours. For more information, see Traffic playback and stress testing.
SQL Review: This feature supports global workload analysis on SQL statements. It helps you quickly locate suspicious SQL statements, analyzes suspicious SQL statements, and provides the corresponding optimization suggestions. For more information, see SQL Review.
Transaction analysis: You can use the transaction analysis feature to obtain the transaction type, number of transactions, and transaction details of a thread within the specified period. This allows you to understand, analyze, and optimize database performance at the transaction level. For more information, see Transaction analysis.
Quick transaction analysis: You can use the quick transaction analysis feature to check the start and end SQL statements of the transaction where the SQL statement to be analyzed is located. This way, you can obtain the commit or rollback status of the SQL statement. For more information, see Quick transaction analysis.
Billing
You can use the SQL Explorer and Audit feature only after DAS Enterprise Edition is enabled. For more information about the billing for different versions of DAS Enterprise Edition, see Billing overview.
Enable SQL Explorer and Audit
If you have enabled DAS Enterprise Edition for a database instance, the SQL Explorer and Audit feature is automatically enabled for the database instance. You do not need to manually enable this feature. For more information, see the "Enable DAS Enterprise Edition" section of the Enable and manage DAS Economy Edition and DAS Enterprise Edition topic.
Log on to the DAS console.
In the left-side navigation pane, click Instance Monitoring.
On the page that appears, find the database instance that you want to manage and click the instance ID. The instance details page appears.
In the left-side navigation pane, choose Request Analysis > SQL Explorer and Audit.
On the SQL Explorer and Audit page, click Enable.
If you have not enabled DAS Enterprise Edition for your Alibaba Cloud account, enable DAS Enterprise Edition as prompted. For more information, see the "Enable DAS Enterprise Edition" section of the Enable and manage DAS Economy Edition and DAS Enterprise Edition topic.
Modify the storage duration of data generated by SQL Explorer and Audit
If you reduce the storage duration of data generated by the SQL Explorer and Audit feature, DAS immediately clears the SQL audit logs that are stored for a period longer than the specified storage duration. We recommend that you export and save SQL audit logs to your computer before you reduce the storage duration.
Log on to the DAS console.
In the left-side navigation pane, click Instance Monitoring.
On the page that appears, find the database instance that you want to manage and click the instance ID. The instance details page appears.
In the left-side navigation pane, choose Request Analysis > SQL Explorer and Audit.
On the SQL Explorer and Audit page, click the SQL Explorer tab. On this tab, click Service Settings.
In the panel that appears, modify the storage duration and click Submit.
If you have enabled DAS Enterprise Edition V3, you can modify the storage duration for different sub-features.
NoteYou can also specify the storage duration of data generated by the SQL Explorer and Audit feature for your database instance on the DAS Professional Edition Management page. For more information, see Enable and Manage DAS Economy Edition and DAS Enterprise Edition.
The storage space that is occupied by the data generated by the SQL Explorer and Audit feature is provided by DAS and does not consume the storage of your database instance.
Disable SQL Explorer and Audit
After you disable the SQL Explorer and Audit feature, your business is not affected. However, SQL audit logs are cleared. Before you disable the SQL Explorer and Audit feature, we recommend that you export the SQL audit logs as a file and download the file to your computer. If you enable the SQL Explorer and Audit feature again, SQL audit logs are generated from the point in time when the SQL Explorer and Audit feature is enabled.
Log on to the DAS console.
In the left-side navigation pane, click Instance Monitoring.
On the page that appears, find the database instance that you want to manage and click the instance ID. The instance details page appears.
In the left-side navigation pane, choose Request Analysis > SQL Explorer and Audit.
On the SQL Explorer and Audit tab, click Search.
In the Logs section on the Search tab, click Export.
In the dialog box that appears, configure the Exported Fields and Export Time Range parameters and click OK.
Download the exported file to your device and keep the file safe.
The page on which you can download the data of SQL Explorer and Audit varies based on the version of DAS Enterprise Edition. Download the exported log file based on the actual layout that is displayed.
Click View Exported Logs on the Search tab and download the exported log file.
Download the exported log file on the Task list tab.
Click Service Settings. In the panel that appears, disable the SQL Explorer and Audit feature.
If you have enabled DAS Enterprise V3, clear all features of SQL Explorer and Audit and click Submit.
NoteThe storage space that is occupied by the data generated by the SQL Explorer and Audit feature is released one hour after the SQL Explorer and Audit feature is disabled.
Migrate the data of SQL Explorer and Audit between different versions of DAS Enterprise Edition
Compared with DAS Enterprise Edition V1, the underlying storage architecture of DAS Enterprise Edition V2 is changed. The hybrid storage of hot and cold data is used to increase performance at lower costs. Based on the hybrid storage of hot and cold data, the billable items for DAS Enterprise Edition V3 are divided by features. This makes billing more flexible and greatly reduces costs.
If your database instance supports DAS Enterprise Edition V3, you can migrate data from DAS Enterprise Edition V1 or DAS Enterprise Edition V2 to DAS Enterprise Edition V3. This way, you are charged in a more cost-efficient manner. For more information, see the "How do I migrate data between different versions of DAS Enterprise Edition?" section of the FAQ topic.