You can use the storage analysis feature of Database Autonomy Service (DAS) to view the storage profile of a database instance, the available days of storage space, and the space usage, space fragmentation, and space anomaly diagnosis of a table in the database. This topic uses ApsaraDB RDS for MySQL databases to describe how to use the storage analysis feature.

Prerequisites

The storage analysis feature is available for MySQL and MongoDB databases.
Note MySQL databases can be ApsaraDB RDS for MySQL databases or PolarDB for MySQL databases. MongoDB databases can be ApsaraDB for MongoDB databases or self-managed databases.

View the storage analysis of a single database instance

  1. Log on to the DAS console.
  2. In the left-side navigation pane, click Instance Monitoring.
  3. Find the instance that you want to view, and choose Performance > Storage Analysis in the Actions column.

    Instance monitoring

    1. Choose Storage Analysis > Storage Overview. On the Storage Overview tab, you can view the overall information, such as Storage and Storage Trend.
    2. Choose Storage Analysis > Data Space. On the Data Space tab, view storage usage details of each database and table. Click a table name to view the fields and indexes of the table.

View global storage usage

If you have multiple database instances, you can view the storage usage of all database instances on the Global Storage Usage page. On this page, you can also find the database instance that has the highest storage usage in a few clicks.

Note The global storage usage feature is available only for ApsaraDB RDS for MySQL databases, self-managed MySQL databases, ApsaraDB for MongoDB databases, and self-managed MongoDB databases.
  1. Log on to the DAS console.
  2. In the left-side navigation pane, click Storage Analysis to go to the Global Storage Usage page and view the information.
    Note DAS cannot collect storage space information from the self-managed database instances that are directly connected based on accounts and have DBGateway deployed. Therefore, the Global Storage Usage page cannot display information about these database instances.