Data Management (DMS) allows you to change schemas without locking tables. This prevents your business from being blocked by table locks and reduces the latency caused by the online DDL feature of MySQL during primary-secondary replication. The feature creates one or more temporary tables that use the new schema, replicates full data and incremental binary log data to the temporary tables, and then stores the temporary tables as permanent tables.
The database instance is managed in Stable Change or Security Collaboration mode in DMS. For more information, see Control modes.
The lock-free schema change feature is enabled for your database instance. For more information, see Enable the lock-free schema change feature.Note
In the following example, this feature is enabled for an ApsaraDB RDS for MySQL instance in a simulated development environment.
In the following example, the data type of the
long_text_a column in the
big_table table is changed from
Submit a ticket as a regular user.
Log on to the DMS console V5.0 as a regular user.
In the top navigation bar, choose .Note
If you are using the DMS console in simple mode, move the pointer over the icon in the upper-left corner of the console and choose All functions > Database Development > Data Change> Lockless change.
Set the parameters that are described in the following table and click Submit.
Required. The database in which you want to change data. In this example, the
poc_devdatabase in Secure Collaboration mode is selected.
Required. The reason for the data change. This helps you find the ticket in subsequent operations.
Required. The purpose or objective of the data change. This reduces unnecessary communication.
Required. The method in which you want the ticket to be submitted for execution. Select Last Auditor Execute.
Required. The estimated number of data rows that will be affected by the data deletion operation. To obtain the actual number of affected rows, you can use the
COUNTfunction in SQL statements and execute the SQL statements on the SQLConsole tab.
SQL Statements for Change
Required. The SQL statement that you want to execute to change data. In this example, the following
ALTERstatement is executed:
ALTER TABLE `big_table` MODIFY COLUMN `long_text_a` text(1024) NULL AFTER `name`;Note
This statement changes the data type of the
SQL Statements for Rollback
Optional. The SQL statement that you can execute to roll back the data change.
Optional. The stakeholders involved in the data change. All specified stakeholders can view ticket details and assist in the approval process. The users that are not specified are not allowed to view the ticket details (except for DMS administrators and DBAs).
On the Ticket Details page, confirm the ticket details.Note
You can view the ticket details on the Ticket Details page. DMS prechecks the SQL statement that you want to execute. The precheck items include the syntax of the SQL statement, whether the type of the SQL statement matches the type that you configured in the security rules, the permissions of the user who submitted the ticket, and the estimated number of rows to be scanned.
After the ticket details are confirmed and the precheck is complete, click Submit for Approval. In the message that appears, click OK.Important
You can modify the ticket details only before you submit the ticket for approval.
Approve the ticket as a DMS administrator.
Log on to the DMS console V5.0 as a DMS administrator.
On the Home page of the DMS console, click Pending Tickets in the My Tickets section.
On the My Tickets page, find the ticket that you want to handle and click the ticket number in the Ticket Number column.
In the Ticket Details panel, confirm the data change information in the ticket and click Approve.
In the dialog box that appears, enter comments and click Submit.
Execute the ticket as a regular user.
Log on to the DMS console V5.0 as a regular user.
In the Execute section in the Ticket Details panel, click Execute Change. In the dialog box that appears, set the parameters that are described in the following table and click Confirm Execution.
Specifies whether to execute the task immediately or at a scheduled time. Valid values:
Running immediately: DMS runs the task immediately after you submit the task.
Schedule: DMS runs the task at the scheduled time that you specify.
Default value: Running immediately.
Specifies whether to enable transaction control. Valid values:
on: If an SQL statement fails to be executed, all the executed DML statements in the same transaction are rolled back. DDL statements cannot be rolled back.
off: One SQL statement is executed at a time. If an SQL statement fails to be executed, the transaction is stopped. The other executed SQL statements in the same transaction are not rolled back.
Default value: off.
Specifies whether to back up data. Valid values:
on: DMS generates
INSERTscripts to back up the data that will be affected when
DELETEstatements are executed.
off: No backup scripts are generated for the preceding data.
Default value: on.Note
After you click Confirm Execution, DMS starts to run the task.
View the task progress and verify the schema
Move the pointer over the name of the database to be changed in the Basic Information section as a DMS administrator. In the menu that appears, click Query.
You are automatically redirected to the page of SQL Console.
On the SQL Console tab, enter an SQL query statement in the SQL editor. Then, click Execute in the upper part of the SQL editor.
For example, you can enter the following SQL statement to query the tables of the current database.
When DMS changes the schema of a table without locking tables, two temporary tables are generated.
- In the top navigation bar, choose .
Click the task number of the task that you want to manage. The Execution details dialog box appears.
Click Progress in the Operation column.
In the Lock-Free structure change message, view the progress information of the task.
After the task is complete, verify the schema.
The schema of the
big_tabletable is changed, and the temporary tables are deleted.