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
- Remove all currently installed SQL Tools components from your system.
2. Install the Required Version of SSMS
- 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
- 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.
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 ...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 ...Missing Timestamp for a Comparison Execution
If you're looking to track when a comparison was executed in dbForge Data Compare for PostgreSQL, note that there is no dedicated timestamp log for each operation. However, there is a related setting that can help: You can enable automatic restore ...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 Generate a "dump_crash" for SSMS, Including Add-in Tools
If SQL Server Management Studio (SSMS) crashes, it’s possible to configure your system to automatically generate a memory dump file. This file is essential for identifying issues related to both SSMS and integrated tools such as SQL Complete. This ...