After you change the schema of a table in a database in Data Management (DMS), DMS adds the latest schema to the schema version list of the database. You can download and compare schema versions, and restore a historical schema version in the schema version list.

Overview

Schema versions are defined based on a database and store the schema information of all the tables in the database. If the schema of a table in the database is changed, a new schema version is saved. For more information, see Save new schema versions.

Assume that a database instance that is managed in Security Collaboration mode has five databases. Each database can contain 50 schema versions. In other words, for a database instance that is managed in Security Collaboration mode, a maximum of 50 schema versions can be retained for each database in the instance.

Usage notes

  • The following database engines are supported:
    • MySQL series: native MySQL, ApsaraDB RDS for MySQL, PolarDB for MySQL, PolarDB-X, AnalyticDB for MySQL, and ApsaraDB OceanBase for MySQL
    • PostgreSQL series: native PostgreSQL, PolarDB for PostgreSQL, and AnalyticDB for PostgreSQL
    • PolarDB-O
    • SQL Server
    • MariaDB
  • The following content shows the maximum number of schema versions that can be retained for each database in database instances that are managed in different control modes:
    • Flexible Management: 3
    • Stable Change: 20
    • Security Collaboration: 50
  • You cannot manage schema versions for the following databases:
    • Databases that contain more than 1,024 tables
    • System databases such as the information_schema and system databases in a MySQL database instance

Procedure

  1. Log on to the DMS console.
  2. In the left-side instance list of the DMS console, click the database instance where the database that you want to manage resides, right-click the database, and then select Version management.
    The Database version list tab appears.
    Note You can also go to the Database version list tab by using the following methods:
    • On the SQLConsole tab of the database that you want to manage, move the pointer over the Share icon icon and select Version management.
    • On the Database List tab of the Instance tab, find the database that you want to manage, move the pointer over More in the Actions column, and then select Version management. You can use this method to go to the Database version list tab only as a DMS administrator or database administrator (DBA).
  3. On the Database version list tab, find the version number of the schema that you want to manage. You can perform the operations that are described in the following table.
    Action Description
    View View the detailed information of the schema version.
    Preview script Preview the SQL script that is used to generate the schema version.
    Table structure comparison Synchronize the schema version to another database, or compare the schema version with a schema version in another database. For more information, see Synchronize schemas.
    Structural recovery Synchronize the schema version that you want to restore to an empty database. For more information, see Initialize empty databases.
    Database version list

Save new schema versions

New schema versions are saved when the following operations are performed in DMS:
Note
If the schema of a table in a database is changed in environments other than DMS, you can perform the following operations in DMS to synchronize the latest schema of the database:
  • If the instance where the database resides is managed in Security Collaboration mode, click the Sync Metadata icon icon in the upper-right corner of the SQLConsole tab to synchronize the latest schema.
  • If the instance where the database resides is managed in Flexible Management or Stable Change mode, click the Refresh icon icon in the upper-left corner of the SQLConsole tab to synchronize the latest schema.