Skip to Main Content
Return to Navigation

Copy Compare Overview

The Data Migration Workbench is used to copy and compare projects.

The ability to compare or copy a project is determined by the data set definition parameter Is Copyable. The user initiating the copy or compare must also have permission to the data contained in the Data Migration Project.

Data Migration Workbench provides the ability to:

Copy to File

Once the Data Migration project is defined it can be copied to file. The system will prompt you to select the file location from the available file locations defined on the Manage File Locations page. When the copy to file has succeeded, the Project State will be updated to Copy to file succeeded.


Before you can do a compare, the data set definition in for the source and the target must be same. If there is difference in shape of any data set definition referenced in the project then the Compare will be aborted. Shape refers to the metadata describing the data migration project, including the data set definition itself, the record definitions that are part of the data set definition, and the fields that are part of the records that are part of the data set definitions.

Compare looks for the following type of differences:

  • Row Difference – Based on the record keys compares if the row exists in both the source and target databases. All differences will be captured and shown as Absent on the database where the key is not present.


  • Field Difference – The value of a field differs between source and target.

Comparing From File

When you select to compare, the system performs the following:

  1. An application engine program is executed that copies each data set instance in the Data Migration Project from XML to memory as a PeopleSoft rowset (not to the database) and the corresponding object is copied from SQL to memory as a different PeopleSoft rowset.

  2. The two in-memory rowsets are then compared record-by-record, row-by-row, and field-by-field

    In this case the file is the source and the local node is the target.

  3. Any differences found in compare are stored in a table on the target database.

    Note: It is stored in the same table used for managed object compare.

  4. The differences found can be seen by running the compare viewer, which reads the compare output table.

Using Compare Viewer

Once the compare is completed, you can use the viewer to view differences and determine which data set instances you want to include in the copy.

Copy from File

Once you have reviewed the compare reports on the target database and selected which data set instances in the project should be copied, you can submit the data migration project for copy. If approval workflow has been configured for the Data Migration Workbench, you will receive a message that the project has entered the approval workflow. If approvals are not required for the project or when all approvals have been obtained, the copy will be scheduled to run through the Process Scheduler.