プライバシーポリシー
データ処理とセキュリティ契約
Changing Data
フォーカスモード
フォントサイズ
DMC supports data change in databases through SQL operations. Data change supports SQL statements such as CREATE, INSERT, UPDATE, DELETE, and TRUNCATE.
Operating Procedures
The data change process is as follows:
1. Submit a ticket request: Select the instance, database, and execution method, then input the SQL to be executed.
2. Preview and SQL check: After the ticket is submitted, the system automatically performs an SQL check in the following sequence: SQL syntax check, and automatic SQL review. If there are syntax errors, or items requiring improvement, manual intervention is needed before proceeding to the Approval step.
3. Approval: After the SQL check is completed, conduct manual approval.
4. Execution: After approval, proceed with either automatic execution or manual execution of the SQL.
5. Complete: After execution is completed, review the execution results and logs.
Prerequisites
If operating users are regular DMC users, they need to apply for or be granted database change permissions. For related operations, see Apply for Instance Permissions (Regular User), Batch User Authorization (Administrator), or View and Reclaim Instance Permissions.
Directions
1. Log in to the DMC console.
2. In the top menu bar, select Data Management > Data Modification.
3. On the Submit a ticket page, configure the ticket parameters.
The main configuration parameters are described as follows:
Parameter | Description |
Instance | Select the database instance to be changed. |
Database | Select the database to be changed. |
Execution Mode | Select the approval execution method, including Auto-execute after approval and Manually execute after approval. |
Execute SQL | Enter executable SQL statements in the text box. Separate multiple SQL statements with a semicolon (;). |
4. Once the configuration is complete, click Submit.
After the ticket request is submitted, the system will automatically perform an SQL check.
5. On the Ticket Management page, check the ticket status. Different statuses correspond to different operations.
Ticket statuses include SQL check failed, and SQL check passed.
SQL check failed: Indicates an error in the SQL syntax. Click Modify in the corresponding operation column of the ticket to view ticket details and error information. Then, click Modify SQL Statement , make the necessary corrections, and resubmit the ticket. You can proceed to the next step till the status updates to Reviewing.
SQL check passed: Indicates that the execution SQL requires improvement. Click View Details in the corresponding operation column of the ticket to view ticket details and check information. You can choose to modify SQL or directly submit for approval.
Modify SQL: Click Modify SQL Statement, make the necessary corrections, and then click Submit.
Directly submit for approval: In the SQL Execution Ticket dialog box, click Submit for Review.
6. Wait for the approval to be completed before proceeding to the next step. For details on ticket approval operations, see Approve Work Order.
If the ticket status is Rejected, click View Details in the operation column to check the rejection reason.
7. (Optional) On the Ticket Management page, click Execution in the Operation column of the ticket to be executed. In the SQL Execution Ticket dialog box, click Execute Now. When the ticket status shows Execution Successful, it indicates that the data has been successfully changed.
If the Execution Mode selected during ticket submission is Auto-execute after approval, the submitted SQL statements will be executed automatically without requiring this step. When the ticket status displays Execution Successful, it indicates that the data has been successfully changed.
8. On the Ticket Management page, click View Details in the Operation column corresponding to the executed ticket.
View ticket details, execution results (either execution failure or execution successful), and execution logs.
フィードバック