Execution and sessions

The Execution stage, session files, and re-running a saved configuration.

Execution stage

The Execution stage runs the migration or synchronization and shows progress.

Pick a session name from the Session name combo box, or accept the default (New session [DD-MM-YYYY HH.MM.SS]). Click Save to store the current configuration as a session.

Session name combo box

Save options

  • Save settings automatically on Commit - tick this checkbox and DBConvert will save the session every time you press Commit.
  • Automatic structure update in the session - tick to refresh the source structure when the session is reopened. New fields and tables in the source will then be carried over without reconfiguring.
  • Handle only selected tables in the session - tick the tables you need in the tree, enable this option, save the session. Subsequent runs of this session only transfer the chosen tables. Works for existing sessions too - load, tick, re-save.

Running the job

Click Commit. Two progress bars show total progress and current-operation progress. When the total bar hits 100%, the run is complete.

Execution stage running

Review the log and any errors that surfaced during the run. Log files are saved under:

C:\Program Files\DBConvert\<product>\LOG

Saving and reusing sessions

A session stores the source and target connection settings, the chosen objects, and the customization options. After the first session is saved, the application shows a Sessions stage at startup with the list of saved sessions.

Session files use the .sav extension. Default location for DBConvert for MySQL & PostgreSQL:

C:\Program Files (x86)\DBConvert\MySQL2PostgreSQLPro\MySQL2PostgreSQLPro Sessions

Sessions stage

The source and destination summaries on the right update for each selected session.

Buttons

  • New → opens Source and destination connections for a fresh job.
  • Load → restores the selected session's source, target, and option settings for review or editing.
  • Execute → loads the session and jumps straight to the Execution stage for an immediate run.
  • Delete removes an obsolete session.

Re-running from the command line

Once a session is saved, you can run it without the GUI:

C:\Program Files\DBConvert\MSSQL2MySQLPro\MSSQL2MySQLPro_Cons.exe /Session:"Session Name"

For details, see Command-line mode. To run a session on a schedule, see Built-in scheduler.