Auto-fill logs will open a directory selection dialog, then generate all the log files' paths for you.

Log strategy

Users have differing expectations of the log file generation so Full Convert supports a variety of approaches:

• No logging
• Overwrite - on each run, log files are truncated before being written to
• Timestamped folder - on each run, a new folder is created with a timestamp in its name, then log files created in it
• Timestamped files - on each run, new files are being created with a timestamp in their names
• Append - log files are never truncated, new data is being written into the same ones

Summary

This contains a high-level overview of the conversion.

Errors

This contains a simple list of all errors, grouped by table.

Warnings

This contains a simple list of all warnings, grouped by table.

SQL

A complete list of all SQL statements sent to the target database. When target database is not relational, this log will be empty. When bulk mode is used, there will be no SQL INSERT statements, because bulk mode bypasses SQL to achieve maximal performance. If you absolutely need to have those statements, force single SQL insert mode. That will be very slow, but is very good for troubleshooting and inspection of data.

Failed SQL

Only SQL statements that caused target database to report an error are saved here. Whenever you get some error not related to data, this is the place to look.

JSON

The richest log. As JSON is structured and hierarchical, we store a lot information in here:

• high-level overview
• performance details for each table
• errors