All Products
Search

This Product

    Data Management:Deal with inconsistent table schemas

    Document Center

    Data Management:Deal with inconsistent table schemas

    Last Updated:Oct 19, 2023

    This topic describes how to solve inconsistencies between the table schema displayed in a schema design ticket and that in the relevant base database.

    Solution

    Remove the table that has the issue from all the associated tickets in the In design state. You do not need to remove this table from the associated tickets whose state is Published or Closed. Procedure:

    1. Log on to the DMS console V5.0.

    2. In the top navigation bar, choose Database Development > Schema Change > Schema Design.

      Note

      If you use the DMS console in simple mode, move the pointer over the 2022-10-21_15-25-22.png icon in the upper-left corner of the DMS console and choose All functions > Database Development > Schema Change > Schema Design.

    3. View the tickets that are associated with the table.

      1. On the Schema Design Tickets page, click a ticket that is associated with the table and is in the In design state.

      2. Move the pointer over the table name to view the associated tickets.

    4. Removes the table from the ticket.

      1. In the section that displays the basic information of the ticket, click the ticket number.

      2. On the Tables Changed in Project tab of the Schema Design step, click Remove from Ticket in the Actions column that corresponds to the table.

      3. Read the information about risk items, and click Confirm Removal.

    5. Edit the table and make sure that the table schema displayed in the schema design ticket is consistent with that in the relevant base database.

      1. Go to a ticket that is associated with the table in the base database and is in the In design state. In the table list on the left, right-click the table name.

      2. Select Design Table and edit the table.

      3. Click Save.

        After you save the modification, the system recollects the metadata of the database to ensure that the table schema displayed in the schema design ticket is consistent with that in the base database.