This topic describes the features that are supported for common users in Data Management (DMS).
Operations in the DMS console
Log on to the DMS console. Submit tickets to apply for permissions on the instance, the database, and the table that you want to manage. For more information, see Permission management.
After your tickets are approved, go to the SQLConsole of the database. In the code editor, write an SQL statement and click Execute. The returned data is displayed as a table below the code editor. You can edit the returned data in the table. For more information, see SQL console and Cross-database query.
Submit tickets to perform operations on data, such as change, import, or export operations. For more information, see Common data change, Import data and Data export.
Features that are supported for common users
Category | Feature | Description |
Permissions | You can apply for permissions on instances, databases, tables, and sensitive fields. You can also view permissions that you have. | |
SQLConsole | You can write SQL statements to query data in a single database. This feature can be used to verify business code, analyze product effects, and identify issues in an online environment. | |
You can perform join queries across online heterogeneous data sources that are deployed in different environments. | ||
Schemas | When you develop or optimize a project or process a new business requirement, you often need to change schemas. For example, you can use this feature when you create a table or modify an existing table. | |
You can use this feature to compare and synchronize the schemas of tables that are stored in different environments, such as online and offline environments. This feature helps ensure the consistency of schemas. | ||
Optimization | You can use this feature to avoid publishing SQL statements that do not use indexes or do not conform to database development standards. This feature helps protect against SQL injection attacks. | |
Data plans | You can submit data change tickets to initialize data for a newly published project, clean up historical data, fix bugs, or run a test. | |
You can submit data import tickets to import a large amount of data to your databases at a time. | ||
You can submit data export tickets to extract a large amount of data for analysis. | ||
If specific data fails to meet your requirement due to reasons such as misoperation, you can use this feature to trace historical data changes. Then, you can execute rollback statements to restore data to the normal state. | ||
Some business scenarios may require you to frequently prepare data. In this case, you can generate test data to ensure data security and discreteness and improve production efficiency. | ||
You can use this feature to clone MySQL databases. |