Stopping Bulk Data Transformation

When you stop the BDT, Data Exchange stops processing the transformation records gracefully. The Data Exchange Runtime Service Tracking Database (Tracking DB) that is created during the installation of the Runtime Service ensures that no transactions are duplicated or lost.

To stop a BDT

  1. Click Manage.

    The hosts associated with the deployed transformations appear on the Source Database Hosts pane.

  2. On the Source Database Hosts pane, expand the relevant host icon, and then expand the required host to view the databases hosted on it.

  3. Select the transformation source of the BDT in progress.

  4. In the Summary tab, click Stop.

When you stop the BDT

To restart the BDT from the beginning

  1. Clear the data from the target data store.

  2. Click Start.

To resume the BDT from where it had stopped, click Resume.

On resuming the transformation, the Statistics page displays only the number of records processed after the transformation was resumed. On completion of the transformation, the Summary tab displays the total number of records processed.

Notes:

  • For RDMS as the transformation source, you can resume the BDT only during the Loading phase of the transformation.

  • For SQL Server as the transformation source, you can resume the BDT only if it was run with the option With Update Lock and if no updates were made to the source database. However, if BDT was run with the option With No Lock, then Data Exchange cannot track the updates in the source database. Hence, a resume will not be possible.

  • For SQL Server as the transformation source, if MSSQLServer service is restarted after the last update to the source table, you will not be able to resume the BDT, even if no updates were made to the source table after BDT stopped. This is because SQL Server does not preserve the timestamp of the last update to the table before it is restarted. Hence, you must start the BDT from the beginning.