dbForge SQL Tools Missing After Installing or Updating SSMS

When launching SQL Server Management Studio (SSMS) for the first time after installing dbForge SQL Tools, a brief initialization process is expected. This typically takes 1–2 minutes depending on system performance. If the tools—such as SQL Complete—do not appear after this time, additional steps may be required to restore integration.

Why SQL Tools May Be Missing

dbForge SQL Tools integrate only with the version of SSMS that is installed at the time of tool setup. If you’ve recently updated or reinstalled SSMS (especially using the official SSMS 21 download) existing integrations may no longer function correctly if the tools were installed prior to the update.

This is a known compatibility behavior and is not indicative of a failed installation.

✅ Troubleshooting Steps

1. Uninstall dbForge SQL Tools

1. Remove all currently installed SQL Tools components from your system.
   

2. Install the Required Version of SSMS

1. Download and install the appropriate version of SSMS for your workflow. For the latest supported features, we recommend using the official SSMS 21 download. Make sure to use the verified ssms installer from Microsoft's website to ensure a stable and complete setup.
   

3. Reinstall dbForge SQL Tools

1. Download the most recent version of dbForge SQL Tools from the official Devart website. Run the installer and follow the prompts to complete the installation.
   

Integration with Visual Studio

The same procedure applies if you are working within Visual Studio (VS). For example, SQL Complete integrates into both SSMS and Visual Studio environments. If the integration fails after a VS update, repeat the uninstall and reinstall process described above.

Applicable Products:

1. SQL Complete
2. Source Control
3. Unit Test
4. Schema Compare
5. Data Compare
6. Data Generator
7. Documenter
8. Data Pump
9. Index Manager
10. Search (free)
11. Monitor (free)

Note: Each version of SQL Tools is designed to be compatible only with the SSMS versions available at the time of its release.

For example, SQL Complete 6.3.16, released on December 18, 2019, works correctly with SSMS 17 and is limited to that version. If you need to download an earlier version of the product, follow the instructions in this guide: How to Download and Install a Previous Version of the Product*

*requires an active or expired subscription

• Related Articles

• CPU Metrics Not Displayed in dbForge Monitor for SQL Server

  Symptoms When using dbForge Monitor for SQL Server, you may observe that CPU metrics are not displayed for certain active connections. For instance, the CPU usage section might be empty or missing data, as illustrated in the example below: The ...

• Troubleshooting T-SQL Debugger Configuration Issues

  T-SQL Debugger in SQL Complete and dbForge Studio for SQL Server depend on a properly configured environment and the required SQL Debugging components. If the debugger does not start, cannot connect to SQL Server, or CheckDebugger reports missing or ...

• Silent installation of ADD-in Tools (i.e., dbForge SQL Complete) with custom IDE selection.

  dbForge SQL Complete can be installed in silent mode (without user interaction) using a configuration file (.ini). This file allows you to define in which IDEs (SSMS or Visual Studio) the integration should be performed. It also includes parameters ...

• 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 Collect Log Files for dbForge SSMS Add-ins

  Applies to: dbForge Search for SQL Server dbForge Index Manager for SQL Server dbForge Monitor for SQL Server dbForge Unit Test for SQL Server Log File Location The log files are stored in the following folder: %AppData%\Roaming\Devart\ Two types of ...