Executing Projects in Parallel

This article describes the best practice approach for executing Precision Bridge projects in parallel from the same Precision Bridge client machine,  It applies to all Precision Bridge source and target adaptors.

1.  Take a copy of the project (using File->Save As) so that each project runs with a unique name. This will prevent any shared log files or project specific information from being over-written which could lead to unexpected behaviour.  For example, if you want to run the same project to migrate customer X and customer Y in parallel then create Project X for customer X and create a copy called Project Y for customer Y.  Each project can have different project variables passed without changing the project definition.

2. We recommend at least 4GB of memory be available for each instance of Precision Bridge that is being executed in parallel.

3. If parallel projects are connecting to the same source/target it is recommended that a different account is used to connect in each case.  This will prevent any issues relating to simultaneous API calls from the same user.

4. For Precision Bridge v5.4 or earlier the licence key needs to be applied for each Windows user connecting to the Precision Bridge client machine.  For version 6.0 and above the licence is shared across all users and only needs to be applied once.

5. WIth Precision Bridge 6.0 or later, you can take advantage of the command-line execution option to schedule multiple migration runs in parallel.