Updated on 2023-03-28 GMT+08:00

Adding Login Information

Scenarios

This section describes how to add database login information so that you can log in to a database for visualized data management operations.

  • If you have not logged in to a DB instance through the created login over a year, the system automatically clears all information, including the saved password, of this login.
  • You can log in to the same database either on the DAS console or using other clients. Both methods do not affect each other.
  • DAS allows you to manage DB instances of different types of engines. An RDS for MySQL instance is used in the following example.

Adding Login Information for RDS DB Instances

  1. In the navigation pane on the left of the DAS console, choose Development Tool to go to the login list page.
  2. Click Add Login.
  3. On the displayed page, select the DB engine, source database, and target DB instance, enter the login username, password, and description (optional), and enable Collect Metadata Periodically and Show Executed SQL Statements.

    • After you specify Source Database, the system automatically lists all the DB instances from this source under the current account.
    • The username and password required for adding the login are the database username and password.
    • To delete the password, you can modify or delete the login.
    • You are advised to enable Collect Metadata Periodically. If it is disabled, DAS obtains only the structured data from databases in real time, and the performance of databases is affected.

      The collection time cannot be customized. Once Collect Metadata Periodically is enabled, DAS automatically collects metadata at 20:00 every day (UTC time). If you are not using a UTC time, convert the time according to your local time zone. You can also click Collect Now to collect metadata at any time you want.

    • You are advised to enable Show Executed SQL Statements. With it enabled, you can view the executed SQL statements under SQL Operations > SQL History and execute them again without entering the SQL statements.

  4. Test the connection as needed. If a message indicating that the connection failed is displayed, modify the connection according to the failure causes contained in the message.
  5. Click OK.