How to Enable Logging for Studios, Standalone Tools, and MiniTools
Logging is essential for capturing detailed information about failures and issues within the software. If reproducing or diagnosing a problem is difficult, or if deeper investigation is needed, logging can help gather more information for troubleshooting.
Applicable Products:
Studios:
- dbForge Studio for SQL Server
- dbForge Studio for MySQL
- dbForge Studio for Oracle
- dbForge Studio for PostgreSQL
Standalone Tools:
- dbForge Data Compare for SQL Server
- dbForge Schema Compare for SQL Server
- dbForge Data Generator for SQL Server
- dbForge Query Builder for SQL Server
- dbForge Documenter for SQL Server
- dbForge Event Profiler for SQL Server
- dbForge Transaction Log
MiniTools:
dbForge Schema Compare for MySQL
dbForge Data Compare for MySQL
dbForge Data Generator for MySQL
dbForge Documenter for MySQL
dbForge Query Builder for MySQL
dbForge Schema Compare for Oracle
dbForge Data Compare for Oracle
dbForge Data Generator for Oracle
dbForge Documenter for Oracle
dbForge Schema Compare for PostgreSQL
dbForge Data Compare for PostgreSQL
Steps to Enable Logging:
Open the Options Window:
- In the main menu, select Tools -> Options.... This will open the Options window.
Navigate to the Logging Options:
- In the Options window, go to Environment -> Output.
Enable Logging:
- Select the following options:
- Write queries sent by the program to the SQL Log.
- Log application errors.
Preserve Logs:
- Uncheck the option Delete application log after closing.
Reproduce the Issue:
- After enabling logging, reproduce the issue you are experiencing.
Locate the Log File:
- Once the issue has been reproduced, send the latest
.log file from the following folder:%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\current_product\- Example:
%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\dbForge Studio for MySQL\
Related Articles
How to Start dbForge Products with Logging for Studios, Standalone Tools, and MiniTools
If a dbForge product crashes or becomes unresponsive upon startup, logging is required for a detailed record of failures and issues. This guide helps you launch dbForge products with logging enabled to capture essential information for ...
How to Create a Dump File from Task Manager for Studios, Standalone Tools, and MiniTools
If you encounter issues with Studios, Standalone Tools, or MiniTools, you can generate a dump file using Task Manager for further troubleshooting. Follow these steps to create a dump file. Steps to Create a Dump File from Task Manager: Reproduce the ...
How to Create a Dump File from Task Manager for Studios, Standalone Tools, and MiniTools
If any of the following products become unresponsive or remain in Task Manager marked as "Not Responding," you can generate a dump file to help in troubleshooting. This applies to both Studios, Standalone Tools, and MiniToolsю Steps to Create a Dump ...
How to Automatically Create a Dump File on Crash for Studios, Standalone Tools, and MiniTools
If a crash occurs, you can configure the system to automatically create a dump file for debugging purposes. Follow the steps below to create the required registry keys for different products, such as dbForge Studio, Standalone Tools, and MiniTools. ...
How to Enable Logging for SQL Complete
Logging is required to capture detailed information about failures and issues in the program. If reproducing or diagnosing a problem is difficult, logging helps in performing a deeper investigation. This guide applies to the following product: ...