Data Management (DMS) provides three control modes for you to manage instances. You can configure the control mode for each database instance.
Overview
Control mode | Description | Scenario | Access method |
Flexible Management |
|
|
|
Stable Change |
|
| |
Security Collaboration |
|
| By default, secure hosting is enabled for a database instance that is managed in Security Collaboration mode. DMS administrators, DBAs, and regular users can log on to the database instance without the need to enter a password. |
Billing
Control mode | Billing method |
Flexible Management | Free of charge. |
Stable Change and Security Collaboration | Specific fees are charged. Both subscription and pay-as-you-go billing methods are supported. For more information about the pricing of DMS and how to purchase the DMS service, see the Billable items and prices section of the "Pricing" topic and Purchase the DMS service. |
Configure the control mode of an instance
Change the control mode of an instance.
NoteIf you change the control mode of an instance from Flexible Management to Stable Change or Security Collaboration, you are charged for the instance. For more information, see Pricing.
The features supported by different control modes vary. Before you change the control mode of an instance, make sure that your business is not affected by the change of control mode. For more information about the features supported by each control mode, see the Features supported by each control mode section of this topic.
Features supported by each control mode
Category | Feature | Flexible Management | Stable Change | Security Collaboration |
Instance management | The database account and password are required for instance logon. | The database account and password are required for instance logon. | Alibaba Cloud account authentication is supported for password-free logon. | |
Y | Y | Y | ||
N | N | Y | ||
N | Y: Source IP addresses must be controlled one by one. | Y: This feature can be globally enabled only over office networks. | ||
N | N | Y | ||
Resource authorization granularity | Permissions on the database instance and database accounts. | Permissions on the database instance and database accounts. | Permissions on databases, tables, columns, and rows. | |
Operation authorization granularity | - | Permissions on features. | Permissions on the query, export, and change operations. | |
Authorization period | - | - | The authorization period can be customized. Permissions are automatically revoked after they expire. | |
Row-level data permission management | N | N | Y | |
Data export | Y | Y | Y | |
Y | Y | Y | ||
Permission verification and process approval | - | - | Y | |
Maximum number of rows exported for free per day | One million | 20 million | Unlimited | |
Maximum number of tables per export | Unlimited | Unlimited | Unlimited | |
Maximum capacity of tables per export | 10 GB | Unlimited | Unlimited | |
Security and specifications | Y: Only part of the feature is supported and SQL statements executed within seven days are audited. | Y: Only part of the feature is supported and SQL statements executed within seven days are audited. | Y: All operations in this module are audited. | |
Y | Y | Y | ||
Y: You are charged for using this feature. Fine-grained permission management is not supported. | Y: You are charged for using this feature. Fine-grained permission management is not supported. | Y: You are charged for using this feature. You can enable this feature in the Sensitive Data module. | ||
N | N | Y | ||
Y | Y | N | ||
Data classification | Y: You are charged for using this feature. You can enable this feature in the Sensitive Data module. | Y: You are charged for using this feature. You can enable this feature in the Sensitive Data module. | Y: You are charged for using this feature. You can enable this feature in the Sensitive Data module. | |
Schema change | N | N | Y | |
Y | Y | Y | ||
Y | Y | Y | ||
N | Y | Y | ||
Data change | N | Y | Y | |
N | Y | Y | ||
N | Y | Y | ||
Y | Y | Y | ||
Y | Y | Y | ||
Risk identification before changes | N | Y | Y | |
Risk management after changes | N | Y | Y | |
Database stability assurance | Binary log files within the previous 1 hour can be tracked and downloaded. | Unlimited. Batch download is supported. | Unlimited. Batch download is supported. | |
N | Y: Review rule configurations are supported, whereas process approvals are not supported. | Y: Review rule configurations and process approvals are supported. | ||
O&M management | N | N | Y | |
N | N | Y | ||
R&D efficiency improvement | Collaborative R&D | N | N | Y |
Cross-instance query | N | N | Y | |
Automatic generation of test data | Y: A maximum of one million rows of data can be generated at a time. | Y: A maximum of 100 million rows of data can be generated at a time. | Y: A maximum of 100 million rows of data can be generated at a time. | |
R&D process approval | N | N | Y: You can customize an R&D process approval based on your business requirements. | |
Logical database configuration | N | N | Y | |
Operations on multiple tables | Y | Y | Y | |
Scheduling of recurring data development task | N | N | Y | |
SQL console | Y | - | Y | |
N | N | Y | ||
Y | Y | Y | ||
Y | Y | Y | ||
N | N | Y | ||
N | N | Y: This feature is supported after the cross-database query feature is enabled. | ||
Y | Y | Y | ||
SQL statements | Y | Y | Y | |
Execution plans | Y | Y | Y | |
Change of the character set | Y | Y | Y | |
SQL query timeout and interruption | N | N | N | |
Limits on the number of rows queried per day | N | N | N | |
Limits on the number of queries per day | N | N | Y | |
SQL statements that can be saved | Y | N | Y | |
Table size threshold for full-table scan | N | N | Y | |
Maximum number of rows returned per query | 3,000 rows. Pagination is supported. | 3,000 rows. Pagination is supported. | 3,000 rows. You can specify whether to enable pagination. | |
Visualization of data query results | Y | Y | Y | |
SQL formatting | Y | Y | Y | |
Smart SQL completion | Y | Y | Y | |
Schema management | Schema comparison | Y | Y | Y |
Schema editing | Y | Y | Y | |
Table schema synchronization | Y | Y | Y | |
Maximum number of data dictionaries exported | 5 | Unlimited | Unlimited | |
Design specifications of table schemas | N | N | Y | |
R&D process of table schemas | N | N | Tables created by other accounts, in other databases, and in self-managed databases support this feature. | |
Three database versions can be retained. | Twenty database versions can be retained. | Fifty database versions can be retained. | ||
Code generator | N | N | Y | |
Data dictionary synchronization | N | N | Y | |
Topologies | - | - | Y |
N: not supported
Y: supported
-: N/A
FAQ
Q: Can multiple instances consume the same quota of the Security Collaboration control mode?
A: Yes. However, the instances cannot consume the same quota of the Security Collaboration control mode at the same time. After DMS completes data or schema changes on an instance that is managed in Security Collaboration mode, the administrator or DBA can change the control mode of the instance that consumes the quota to Flexible Management and then change the control mode of another instance to Security Collaboration.
Q: Can I execute SQL statements such as UPDATE and DELETE statements to change data of instances that are managed in Stable Change mode on the SQLConsole tab?
A: No, you cannot execute such SQL statements on instances that are managed in Stable Change mode on the SQLConsole tab. If you want to change data or schema of an instance that is managed in Stable Change mode, submit a ticket. For more information, see Lock-free data changes and Lock-free schema changes.