Database Autonomy Service (DAS) provides the storage analysis feature. You can use this feature to view the storage usage of a database instance and the number of days for which the remaining storage space is available. You can also view information about the usage, the fragments, and anomaly diagnosis results of a tablespace in a database. This topic provides an example to describe how to use the storage analysis feature. In this example, an ApsaraDB RDS for MySQL instance is used.
- Log on to the DAS console.
- In the left-side navigation pane, click Instance Monitoring.
- 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, click Storage Analysis. The Storage Analysis page appears. On the Storage Overview and Data Space tabs, you can view the information about the storage usage of the database instance,
such as information about anomalies and the trend chart of space usage. The following table describes the parameters on the Storage Analysis page.
Parameter Description Storage Overview You can view information such as the average daily space usage within the most recent seven days, the number of days for which the remaining storage space is available, and the total amount of used space. Data Space You can view the usage of each data space and each tablespace. You can click the name of a table to view the fields and indexes of the table. Storage Trend You can view the data space, used space, log space, and used temporary space. You can click the table name to view the indexes of the table. Exceptions
- Identification of potential overflows of auto-increment primary keys: DAS can automatically identify potential overflows of auto-increment primary keys in ApsaraDB RDS for MySQL databases and ApsaraDB PolarDB MySQL-compatible edition databases.
- Identification of duplicate indexes: DAS can automatically identify duplicate indexes in ApsaraDB RDS for MySQL databases and ApsaraDB PolarDB MySQL-compatible edition databases.
- Identification of tablespace fragments: For more information, see Automatic tablespace fragment recycling.
- Identification of abnormal SQL requests: For more information, see Abnormal SQL request identification.