Execution - Track

Modified on Fri, 13 Oct 2023 at 09:40 PM

A Track is a container for all the elements necessary to execute data migration iterations for one project or part hereof.

These elements include:

  • The code needed: a folder containing the engine libraries deployed as a result of the code generation.
  • An export database: A Sql Server database containing (generated) tables and Sql functionality (generated stored procedures) used by the generated export engine to produce the export result.
  • A Portal database: A SQL Server database used by the Portal Runtime to store the intermediate and results of the data migration as well as the events that occurred for each Busine Object.
  • A ValueSet database: A SQL Server database containing (generated) tables for all ValueSets defined as part of the mapping.

To keep track of all this, hopp also includes a Master database containing all information necessary to manage all the Track.

This information includes.

  • Which migration projects are executed in which tracks
  • Folder locations for the track
  • Database connection string for the track


Once a new engine is loaded, the Track panel provides the options to Set Concurrency limits, Restart, Stop, and Assemblies, as illustrated below.

The context menu provides the options to:

Set ConcurrenciesModify the Max concurrent jobs
RestartRestart the Track to pick up new data
StopStop the Track
AssembliesView the Assemblies loaded into the project

For more on the Track, please use this link.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article