At the top of the Log tab, you can choose to log information about the execution of your SQL statements to the GUI or to a file.
If you choose to log to file, you can enter the file path in the text field or click the button to the right of the field to launch a file browser. By default, the log information is written to the GUI, below the log destination controls.
The Preprocess script checkbox controls preprocessing, as described in the Executing an External Script page.
The log keeps an entry for each SQL statement that has been executed. It provides generic information, such as how many rows were affected and the execution time. The important piece of information is the execution message which shows how the execution of that specific statement ended. If an error occurred, the complete log entry will be in red, indicating that something went wrong.
The detail level in an error message depends on the driver and database that is being used. Some databases are very good at telling you what went wrong and why, while others provide less detail.
Clicking the icon to the left of each log entry selects the corresponding SQL statement in the SQL editor. If the icon is missing it might be that you do not have the Show Message selected in the right-click menu of the Log Tab. The icon also has a right-click menu; Load SQL into Editor with submenus for where to place the SQL (at caret, first, last or replacing the current content), and Load SQL in New Editor.
The Log tab right-click menu contains entries that let you control the log content. Use the Show entries to define which information you want to appear in the log. The Clear entries are used to remove certain kinds of results from an existing log.
If you enable the Auto Clear Log control, the SQL Commander automatically clears the log between executions.