How to View System Information in dbForge Products

To help diagnose issues or provide system details to Devart support, you can easily access the system information in your dbForge product. Here's how:

1. Open the dbForge product you are using (this applies to standalone tools like Studio for MySQL as well as SSMS add-ins like SQL Complete).
2. Go to the main menu and click on Help.
3. From the dropdown menu, select About.
4. In the About window, click View System Info.

​

If needed, you can copy or send the system information to the Devart team along with a description of the issue you're experiencing for further assistance.

• Related Articles

• Limit of activations exceeded (dbForge)

  When you change hardware components, reinstall the operating system, or switch user profiles on your computer, the Hardware ID may change. As a result, the software may treat it as a new installation on a different machine. Please also note that ...

• Timestamps Not in Expected Timezone in dbForge Studio for Oracle

  If you're encountering timestamps that don't match your system's timezone in dbForge Studio for Oracle, this can typically be resolved with a quick configuration update. This issue may arise due to default formatting settings or discrepancies in how ...

• How to Activate a Trial Version in dbForge Products

  Starting from release 2025.1, the method of using the trial version and Express Edition has been updated for all paid dbForge products. To help you get started smoothly, please follow the step-by-step instructions below. As of version 2025.1, ...

• 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 ...

• Transaction Notification Is Not Displayed When VIEW SERVER STATE Is Missing

  The Notification if execution contains open transactions option works as expected on some SQL Server instances, but does not display any notifications on others. This behavior is typically caused by the absence of the VIEW SERVER STATE privilege for ...