DMS provides database administrators (DBAs) with tools to register and govern database instances, define development standards, and grant controlled access to developers and O&M engineers.
Get started in the DMS console
Step 1: Register your database instances
Log on to the DMS console and register each database instance you want to manage. For details, see Instance management.
Step 2: Configure security rules
Security rules define your team's database development standards, allowed SQL patterns, and approval workflows. Configure rules for each instance based on your governance requirements.
Only instances managed in Security Collaboration mode support custom security rules.
See Manage security rules and Configure approval processes.
Step 3: Grant user permissions
Grant developers, O&M engineers, and other users access to specific databases and tables. For details, see Permissions.
Features available to DBAs
The following table lists all DMS features available to the DBA role, organized by category.
| Category | Feature | Description |
|---|---|---|
| Data assets | Instance management | Register, view, and modify database instances. |
| Asset category | Classify tables to help DMS administrators, developers, and O&M engineers manage and locate data assets. | |
| SQL console | Single database query | Write and run SQL statements against a single database to verify business logic, analyze product behavior, and diagnose issues in production. |
| Cross-database query | Run join queries across heterogeneous databases deployed in different environments. | |
| Database development | Schema design | Change schemas — such as creating or modifying tables — when developing new features or optimizing existing projects. |
| Database and table synchronization | Compare and synchronize table schemas across online and offline environments to keep schemas consistent. | |
| Data changes | Submit data change tickets to initialize data for new projects, clean up historical records, fix bugs, or run tests. | |
| Data import | Submit tickets to import large volumes of data to a database in a single operation. | |
| Data export | Submit tickets to export large volumes of data for analysis or downstream use. | |
| Data tracking | Restore data to a correct state after accidental modifications or operational errors. | |
| Test data generation | Generate test datasets that are statistically dispersed, reducing time spent preparing test data while keeping production data secure and discrete. | |
| SQL review | Block SQL statements that lack indexes or violate development standards before execution, and prevent SQL injection attacks. | |
| Database cloning | Clone MySQL databases. | |
| Data Transmission Service (DTS) | Task orchestration | Build task flows with one or more task nodes, then schedule and run them to automate complex data pipelines and improve development efficiency. |
| Security and specifications | Security rules | Define which SQL statements are permitted. Only statements that conform to configured security rules can be executed. |
| Approval processes | Configure approval workflows tied to security rules. Different ticket types can follow different approval paths. | |
| Operation audit | Review operation logs that record who performed each change, what was changed, and when. | |
| Sensitive data management | Apply masking algorithms to sensitive fields and adjust sensitivity levels to control data exposure across user roles. | |
| Data watermarks | Embed or extract watermarks in data to trace its origin during distribution. | |
| Permission management | Apply for and manage permissions on instances, databases, tables, and sensitive fields. | |
| Solutions | Create data warehouses | Set up real-time data synchronization to an AnalyticDB for MySQL database in seconds using the one-click data warehousing feature. |
| Data archiving | Regularly archive data from large tables to other databases, then remove it from the source table to reclaim tablespace. | |
| Database migration | Create a migration ticket, run pre-migration checks, and remove the source database after migration completes. | |
| O&M management | Notification | Set up notification rules to subscribe to DMS events and route alerts to the right recipients. |
| Database grouping | Apply a data change or schema design to all databases in a group at once. | |
| Manage tasks | Create, start, and stop tasks from a central view. | |
| Intelligent O&M | View tenant-level statistics on tickets, queries, users, and metadata to monitor the overall health of your DMS environment. |