The cutover testing feature allows you to synchronize the task changes of the source database and the destination database, stop forward synchronization tasks, and prepare for data rollback. This topic describes the procedure of cutover testing.

Prerequisites

Business testing is complete. For more information, see Perform business testing.

Cutover testing

  1. Check Incremental Synchronization Tasks

    You need to synchronize the task changes of the source database to the destination database.

  2. Stop Applications and Modify Settings

    You need to stop the applications and database connection, and modify application configurations.

    Note ADAM allows you to query the connection status of the database. If the value of the Session parameter becomes 0, the applications are stopped.
  3. Stop Source Database Tasks and Trigger

    After you stop the applications and modify application configurations, you need to stop the tasks and triggers of the source database. This prevents the data of the source database from changing.

  4. Stop Forward Synchronization Tasks

    You need to stop the tasks that synchronize data from the source database to the destination database.

  5. Auto Increment Schemas

    You can synchronize the data changes of the source database to the destination database.

  6. Start Reverse Synchronization Data Links

    The step is designed as the preparations for rollback testing. You need to create a Data Transmission Service (DTS) task to synchronize the data of the destination database to the source database. This ensures that invalid data can be rolled back.

  7. Start Destination Database Tasks and Trigger

    You need to start the tasks and triggers of the destination database.

  8. Start Applications

    Before you start the applications, you must make sure that the connection of the destination database is running as expected.

What to do next

In the Start Applications step, click Next to perform rollback testing. For more information, see Perform rollback testing.