Data Management (DMS) allows you to submit data change tickets when you initialize
data for a newly published project, clear historical data, fix bugs, or run a test.
This topic describes the Normal Data Modify feature of DMS. You can use this feature
to perform INSERT
, UPDATE
, DELETE
, and TRUNCATE
operations to change data.
Prerequisites
A database instance is managed in Stable Change or Security Collaboration mode. For more information, see Control modes.
Procedure
Change the valid values of parameters in a data change ticket
To customize the approval process, you can change the valid values of the Reason Category and Execution Method parameters in a data change ticket.
Tips
- After you submit a data change ticket for approval, you can close the ticket when the ticket is approved or rejected. This helps prevent accidental execution after the ticket is approved.
- Approval rules are configured by DMS administrators and DBAs. If you are a DMS administrator or a DBA, click the Security and Specifications tab in the top navigation bar of the DMS console. Then, click Security Rules in the left-side navigation pane to configure approval rules for data change tickets. We recommend that you submit tickets for data changes in the test environment. This way, affected rows can be checked and a backup file can be created for each data change. This allows you to restore data when the data change is not as expected. To ensure high R&D efficiency, you can specify that no approval is required for data change tickets in the test environment.
- You can shard databases and partition tables. If you have configured logical databases, logical tables, and routing algorithms in DMS, you can submit one ticket to shard databases and partition tables at the
same time. You do not need to submit a ticket for each physical database or table.
- If you configure a routing algorithm and include a routing field in the SQL statement that is used to shard databases and partition tables, the routing algorithm routes the statement to the corresponding physical table for execution.
- If you do not configure a routing algorithm, no routing field is included in the SQL statement, or the data type of the routing field does not match the data type that is specified in the routing algorithm, the SQL statement is executed on each table in each database one by one. This process takes a longer period of time.