Data Management (DMS) provides the schema design feature. This feature allows you to design the schemas of tables in a database based on specific R&D standards. You can customize R&D processes for different lines of business based on your business requirements to ensure the consistency of schemas among multiple environments, such as the development environment, test environment, and production environment. This topic describes how to use the schema design feature. In the following example, a physical database is used.
- The database is of one of the following types:
Note This feature supports both physical databases and logical databases.
- MySQL: ApsaraDB RDS for MySQL, PolarDB for MySQL, MyBase for MySQL, PolarDB for Xscale, and MySQL databases from other sources
- The database instance to which the database belongs is managed in Security Collaboration mode. For more information, see View the control mode of an instance.
The following operations describe how to create a table by submitting a schema design ticket, and synchronize the table schema to the
poc_dev destination development database and the
poc_prod destination production database. This topic provides references for you to quickly learn how to use the schema design feature of DMS. For more information, see Design schemas.
Step 1: Create a schema design ticket
- Log on to the DMS console V5.0.
In the top navigation bar, choose .Note
If you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner of the DMS console and choose.
On the Schema DesignTickets page, click Schema Design in the upper-right corner.
Set the parameters for creating a schema design ticket and click Submit. The following table describes the parameters.
The name of the project. Enter a name that can help you identify the project.
The business background of the project, such as the purpose or objective of the project. This reduces unnecessary communication.
Change Base Database
The database on which you want to perform schema design operations. In this example, a database in Security Collaboration mode is selected. The type of the environment in which the database resides must conform to the R&D standards that corresponds to the security rules of the database. For more information about the R&D process, see Schema design. In this example, the
poc_devdevelopment database is used as the change base database.
The security rules that you want to apply. DMS automatically selects security rules after you specify a database.
The iteration to be associated with the project. To select an iteration, click Select/Change Iteration. In the Iterations dialog box, find the iteration and click Associate in the Actions column.
The stakeholders of the schema design. All the specified stakeholders can view the ticket details and assist developers in the development and approval processes.Note
Irrelevant users other than DMS administrators and database administrators (DBAs) are not allowed to view the ticket details.
Step 2: Create a physical table
Create a physical table
In addition to the following methods, you can create a physical table on the SQLConsole tab. For more information, see the "Create a table" section in Manage the Wide Column model in the Tablestore console.
Use the GUI
Click Create Physical Table.
Enter the basic information about the table and modify the fields and indexes of the table.
Execute SQL statements
Click Import SQL Statements.
In the dialog box that appears, enter the
ALTER TABLEstatement as required and click OK.
For example, you can execute the following statement to create a table named
CREATE TABLE `data_modify` ( `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT COMMENT 'Primary key', `name` varchar(256) NOT NULL COMMENT 'Name', `phone` varchar(32) DEFAULT NULL COMMENT 'Phone number', `sex` varchar(32) DEFAULT NULL COMMENT 'Gender', `email` varchar(256) DEFAULT NULL COMMENT 'Email address', `remarks` varchar(1024) DEFAULT NULL COMMENT 'Remarks', PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Personal information';
On the Create Physical Table: data_modify tab, confirm the table information and schema and click Save.
In the Precheck Result message, view the precheck result.
If the precheck is passed, click Confirm Changes and Submit to Save.
If only a warning is displayed, click Ignore the warning and continue to save.. Alternatively, click Close, modify the table schema based on the R&D standards, and then click Save.
If an error is reported, check the cause of the error, click Close, modify the table schema based on the R&D standards, and then click Save.
DMS verifies the preceding SQL statements for table creation or modification based on the R&D standards that are configured in the default security rules, and then reports errors and warnings, if any.
DMS provides nearly 40 R&D standards to help you create tables and modify fields and indexes. You can configure the R&D standards in security rules as required.
After the precheck is passed, you are navigated to the Project Homepage tab. On the Tables Changed in Project tab, you can view the table that you modified or created and modify or delete other tables as required.
Step 3: Apply the schema changes to the destination development database
Click Perform Changes to Base Database.
In the Perform Changes to Base Database panel, view the base database, execution strategy, and schema change script, and click Submit.
After the schema change operation is approved, the system automatically applies the schema changes to the base database.
You can check whether the schema changes are performed as expected on the SQLConsole tab of the base database.
Based on the default security rules, you must submit tickets for schema changes. You can also use custom security rules. For example, you can specify that no approval is required for schema changes in development databases. You can also specify the users who can approve schema change tickets in production databases.
Step 4: Apply the schema changes to the destination production database
Click Perform Changes to Target Database.
In the Perform Changes to Target Database panel, select the destination database, enter script in the Script to Execute field, and then click Submit.Note
You can also click Add Multiple Databases to execute the script in multiple production databases.
After the schema change operation is approved, the system automatically applies the schema changes to the production database. You can check whether the schema changes meet your expectations on the SQLConsole tab of the production database.
Click Go to Next Node. In the message that appears, click Go to Next Node.
After the ticket is closed, you can click each step to view the change and publishing records.