Help Center > > User Guide> TaurusDB for MySQL 8.0 Database Management (Standard Edition)> Overview> Database Management

Database Management

Updated at:May 14, 2020 GMT+08:00


You have logged in to the DAS console.


You can go to the database management page in either of the following methods:

  • In the Database List area, locate the target database and click Manage in the Operation column.
  • Choose Database Management on the top menu bar.
Table 1 Function description




Displays the name of the current database.


Allows you to switch between system and non-system databases.


Displays the IP address, port number, and character set of the current DB instance.


Allows you to open the SQL window of the current database.


Periodically collects metadata such as databases, tables, and fields of the DB instance and stores the data to the databases of DAS.


  • Reduce queries on the user database and the impact on the performance of the user database.
  • Improves the search performance for DB instances that contain a large number of tables and supports pagination queries.


Only structural metadata is collected, which means that user's table data is not included.


Database management consists of three functional modules: object list, SQL tuning, and metadata collection.


Allows you to perform operations.

Object List

You can manage tables, views, stored procedures, events, triggers, and functions of databases. The main operations include creating, querying, and modifying objects.

SQL Tuning

SQL tuning helps you query the SQL statements that are executed frequently, consume a large amount of resources, or take a long time to execute. Therefore, you can optimize operations according to the diagnose results.

  1. On the Database Management page, click the SQL Tuning tab. You can search for SQL tuning history by date to view details or you can add or delete SQL tuning records.
  2. Click Add SQL Performance Tuning. In the displayed dialog box, choose to tune SQL statements or SQL file. If you select SQL Statement, enter the SQL statements and click OK. The tuning results can be viewed in the SQL tuning list.

    • The following types of statements will be changed to the select statements for tuning:

      select ... for update, update ... set ... where ..., delete from ... where ..., and insert into ... select ...

    • Only the select/update/delete/insert statements supports this function. The tuning task that contains unsupported SQL syntax will fail. The following shows the unsupported syntaxes:
      1. alter table t add index idx_name(name);
      2. show databases;
      3. grant SELECT,PROCESS on d.t to 'am'@'%' with grant option;
      4. insert into t(i, v) values (1, 'a').
    • 1. Only the MySQL InnoDB engine is supported.
    • 2. Only the tuning of the select/insert/update/delete statements is supported. The insert statement must contain the select clause.
    • 3. Querying stored SQL statements such as information_schema, test, mysql, is not supported.
    • 4. The view statements are not supported.

  3. In the SQL tuning list, click View Details in the Operation column to view task details.

    You can view the tuning details at the bottom of the task list.

Metadata Collection

In DAS 2.0, metadata of a DB instance such as databases, tables, and files can be automatically collected and stored in the DAS database. In addition, only structural metadata is collected, and the data in your table is not included to protect your data privacy.

  • Metadata collection can reduce database queries which may affect the database performance.
  • Metadata collection also improves the search performance for DB instances that contain a large number of tables and supports pagination queries.
  1. On the Database Management page, click the Metadata Collection tab.
  2. On the displayed page, click Collect to start the collection. You can also stop the collection or view the collection details.

    • Clear the collected data: Clear the collected metadata, database structure, and table structure.
    • Delete Logs: Deleted logs cannot be recovered. Exercise caution when performing this operation.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel