Data Management (DMS) allows DMS administrators to manage system configurations. If you are a DMS administrator, you can modify the system configuration items to flexibly meet your business requirements. This topic describes how to modify the system configuration items.

Prerequisites

You are a DMS administrator. For more information about how to view the role of a user, see View owned system roles.

Procedure

  1. Go to the DMS console V5.0.
  2. On the Configuration Management page, find the configuration item that you want to modify and click Change in the Actions column.
    Note For more information about configuration items, see the Configuration items section.
  3. In the Change Parameter Configuration dialog box, change the value as needed.
  4. Click Confirm Change.

Configuration items

Item Description
Whether to enable access source IP control Specifies whether to enable the IP address whitelist feature for access control. Valid values:
  • Y: enables the IP address whitelist feature. To configure an IP address whitelist, a DMS administrator can click Security and Specifications in the top navigation bar of the DMS console. On the page that appears, click Access IP Whitelists in the left-side navigation pane. Only the access from the specified IP addresses or CIDR blocks in the whitelist is allowed.
  • N: disables the IP address whitelist feature. In this case, the users within the current tenant account can access DMS from all IP addresses.
Note If you use the previous version of the DMS console, perform the following steps to configure an IP address whitelist: In the top navigation bar, move the pointer over the More icon and choose System > Security > Access IP Whitelists.
Whether to enable automatic synchronization of instance resources on the cloud Specifies whether to automatically register all the ApsaraDB RDS instances of the current Alibaba Cloud account with DMS. Valid values:
  • Y: automatically registers all the ApsaraDB RDS instances of the current Alibaba Cloud account with DMS.
  • N: does not automatically register all the ApsaraDB RDS instances of the current Alibaba Cloud account with DMS.
Whether large table archive notification is enabled in SQLConsole Specifies whether to notify users when large tables are archived in the SQLConsole. Valid values:
  • Y: notifies users when large tables are archived in the SQLConsole.
  • N: does not notify users when large tables are archived in the SQLConsole.
Whether to force rollback SQL to be entered when submitting a data change work order Specifies whether to require a user to enter executable SQL statements for rolling back the data change when the user is creating a data change ticket. Valid values:
  • Y: requires the user to enter executable SQL statements for rolling back the data change.
  • N: does not require the user to enter executable SQL statements for rolling back the data change.
Data export reason classification The reason for a data export. The possible reasons are classified into the following categories:
  • Data analysis: You export specific data for analysis.
  • Troubleshooting: You export specific data for troubleshooting.
  • Data synchronization: You export specific data for synchronization.
  • Data test: You export specific data for testing.
  • Business operations: You export specific data to check whether business operation requirements are met.
The whitelist of users who are allowed to create a task flow. Specifies one or more users who are allowed to create task flows.
List of disabled functional modules Specifies one or more features that you want to disable. After a feature is disabled, the entry point of the corresponding operation is hidden.
Access control is enabled for new users by default Specifies whether to enable access control for new users. Valid values:
  • Y: enables access control for new users.
  • N: disables access control for new users.
Whether to enable RAM permission verification Specifies whether to enable RAM permission verification. Valid values:
  • Y: enables RAM permission verification.
  • N: disables RAM permission verification.
Allow sub-accounts to automatically join the tenant Specifies whether to allow RAM users to be automatically added to the current tenant account. Valid values:
  • Y: allows RAM users to be automatically added to the current tenant account.
  • N: does not allow RAM users to be automatically added to the current tenant account.
Whether to force rollback SQL to be entered when submitting a data change work order, Y indicates that rollback SQL must be entered, and N indicates that rollback SQL is not to be force entered Specifies whether to require a user to enter executable SQL statements for rolling back the data change when the user is creating a data change ticket. Valid values:
  • Y: requires the user to enter executable SQL statements for rolling back the data change.
  • N: does not require the user to enter executable SQL statements for rolling back the data change.
Whether to enable the super SQL mode. Specifies whether to enable the super SQL mode. Valid values:
  • Y: enables the super SQL mode.
  • N: disables the super SQL mode.
The timeout period for the number of rows affected by data change verification. The timeout period for calculating the number of rows that may be affected. The value must be an integer. Before a data change is performed, DMS calculates the number of rows that may be affected. The calculation takes a long period of time if the data volume is large. You can specify a timeout period for the calculation in seconds to ensure that the data change can be performed as required. DMS automatically terminates the calculation after the specified timeout period.
Data Change reason classification The reason for a data change. The value must be a JSON string. For more information, see Appendix: Reasons for data changes.
How data changes are performed The method that is used to perform a data change after the ticket is approved. Valid values:
  • COMMITOR: The data change is performed by the user who submits the ticket.
  • AUTO: The data change is automatically performed after the ticket is approved.
  • LAST_AUDITOR: The data change is performed by the last user who approves the ticket.
Whether the approval node of the approval flow automatically eliminates the submitter (valid when there are multiple approvers) Specifies whether to exclude the user who submits a ticket from the list of approvers on an approval node if multiple approvers are assigned on the approval node. Valid values:
  • Y: excludes the user who submits a ticket from the list of approvers on an approval node.
  • N: does not exclude the user who submits a ticket from the list of approvers on an approval node.
Enable workflow approval to exceed your authority (DBA administrator only) Specifies whether to allow a database administrator (DBA) or DMS administrator to act beyond its authority to approve or reject a ticket. Valid values:
  • Y: allows a DBA or DMS administrator to approve or reject a ticket if the previous approver, such as a data owner of the relevant resource, fails to perform the operation.
  • N: does not allow a DBA or DMS administrator to act beyond its authority to approve or reject a ticket.
Default value: Y
Minimum Word Limit for Work Order Business Background The minimum number of characters that are entered to describe the business background of a ticket. If the value is less than or equal to 0, no limits are imposed on the number of characters.
Allow OWNER to authorize users Specifies whether to allow a data owner to grant permissions on data resources to other users. The data resources may be database instances, databases, or tables. Valid values:
  • Y: allows a data owner to grant permissions on data resources to other users.
  • N: does not allow a data owner to grant permissions on data resources to other users.
Maximum number of queries for the day The maximum number of queries that each user is allowed to perform per day. The value must be an integer. After the number of queries that a user performs in a day reaches the specified upper limit, the user cannot perform more queries for the rest of the day. This configuration item applies to all the users within the current tenant account.
Day query rows upper limit The maximum number of data rows that can be returned to each user per day. The value must be an integer. After the number of data rows that are returned to a user in a day reaches the specified upper limit, the user cannot perform more queries for the rest of the day. This configuration item applies to all the users within the current tenant account.
DMS locale: ZH/EN/JA/ZT The language of the operation logs that are returned by DMS. Valid values:
  • ZH: simplified Chinese
  • EN: English
  • JA: Japanese
  • ZT: traditional Chinese

Appendix: Reasons for data changes

DMS provides the following default reasons for data changes, in the format of JSON strings:

[{"key":"config_correct","value":"Modify Config"},
{"key":"project_init_data","value":"Init Project Data"},
{"key":"program_bug","value":"Program Bug"},
{"key":"require_deal_without_backend_function","value":"Requirements Without Backend Function"},
{"key":"history_data_clear","value":"History Data Clean"},
{"key":"test","value":"Test"},
{"key":"mis_operation","value":"Mis Operation"},
{"key":"others","value":"Others"}]

The following table describes the default reasons for data changes.

Key Value Description
config_correct Modify Config Modify configurations.
project_init_data Init Project Data Initialize the data for a project.
program_bug Program Bug Fix a bug.
require_deal_without_backend_function Requirements Without Backend Function Manage the data of an application that does not support backend management.
history_data_clear History Data Clean Clear historical data.
test Test Perform a test.
mis_operation Mis Operation Restore data after an accidental operation.
others Others Change data for other reasons.