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 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 Transaction Log
- dbForge Event Profiler for SQL Server
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
Commands for Running dbForge Products with Logging:
To start the product with logging, use the following commands in Command Line:
Studios:
"C:\Program Files\Devart\dbForge Studio for SQL Server\dbforgesql.exe" /LOG"C:\Program Files\Devart\dbForge Studio for MySQL\dbforgemysql.exe" /LOG"C:\Program Files\Devart\dbForge Studio for Oracle\dbforgeoracle.exe" /LOG"C:\Program Files\Devart\dbForge Studio for PostgreSQL\dbforgepostgresql.exe" /LOG
Standalone Tools:
"C:\Program Files\Devart\dbForge Data Compare for SQL Server\datacompare.exe" /LOG"C:\Program Files\Devart\dbForge Schema Compare for SQL Server\schemacompare.exe" /LOG"C:\Program Files\Devart\dbForge Data Generator for SQL Server\datagenerator.exe" /LOG"C:\Program Files\Devart\dbForge Query Builder for SQL Server\querybuilder.exe" /LOG"C:\Program Files\Devart\dbForge Documenter for SQL Server\documenter.exe" /LOG"C:\Program Files\Devart\dbForge Transaction Log\transactionlog.exe" /LOG"C:\Program Files\Devart\dbForge Event Profiler for SQL Server\eventprofiler.exe" /LOG
MiniTools:
"C:\Program Files\Devart\dbForge Schema Compare for MySQL\schemacompare.exe" /LOG"C:\Program Files\Devart\dbForge Data Compare for MySQL\datacompare.exe" /LOG"C:\Program Files\Devart\dbForge Data Generator for MySQL\datagenerator.exe" /LOG"C:\Program Files\Devart\dbForge Documenter for MySQL\documenter.exe" /LOG"C:\Program Files\Devart\dbForge Query Builder for MySQL\querybuilder.exe" /LOG"C:\Program Files\Devart\dbForge Schema Compare for Oracle\schemacompare.exe" /LOG"C:\Program Files\Devart\dbForge Data Compare for Oracle\datacompare.exe" /LOG"C:\Program Files\Devart\dbForge Data Generator for Oracle\datagenerator.exe" /LOG"C:\Program Files\Devart\dbForge Documenter for Oracle\documenter.exe" /LOG"C:\Program Files\Devart\dbForge Schema Compare for PostgreSQL\schemacompare.exe" /LOG"C:\Program Files\Devart\dbForge Data Compare for PostgreSQL\datacompare.exe" /LOG
How to Run dbForge with Logging:
Open Command Line as Administrator:
- Click Start on your desktop, type cmd, then right-click on Command Line and select Run as Administrator.
Enter the Command:
- Type the relevant command for your product (e.g.,
"C:\Program Files\Devart\dbForge Studio for MySQL\dbforgemysql.exe" /LOG) and press Enter.
Send the Log File:
- After reproducing the issue, locate the log file at the following path:
%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\current_product\- Example:
%SystemDrive%\Users\%UserName%\AppData\Roaming\Devart\dbForge Studio for MySQL\
Submit the Log File:
- Send us the log file for analysis.
Note: The root directory path mentioned is based on the default installation location. If you installed dbForge in a different directory, replace the path to reflect the correct location.
Related Articles
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 ...
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 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 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 ...
dbForge SQL Tools Missing After Installing or Updating SSMS
If dbForge SQL Tools Are Missing After Installing or Updating SQL Server Management Studio (SSMS) Please note that dbForge SQL Tools integrate only with the version of SSMS already installed on your PC. Therefore, if you have updated or installed a ...