dbForge SQL Tools Missing After Installing or Updating SSMS

dbForge SQL Tools Missing After Installing or Updating SSMS

Typically, upon the initial launch of SSMS after you install SQL Tools for the first time, there is a brief registration process that takes no more than 1-2 minutes, depending on your system's performance. If SQL Tools are still missing after this time, please follow the troubleshooting steps below.

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 new version of SSMS, we recommend the following steps:

  1. Uninstall SQL Tools:

    • Ensure that the current version of SQL Tools is completely removed from your device.

  2. Install the Required Version of SSMS:

    • Download and install the version of SSMS you need for your tasks.

  3. Reinstall SQL Tools:

    • Download the latest version of dbForge SQL Tools from the official Devart website and follow the installation instructions.

The same process applies to Visual Studio (VS) when working with dbForge SQL Complete.

By following these steps, you can restore the integration of SQL Tools with the selected version of SSMS or Visual Studio.

Info
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

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

    • Tool Version Does Not Match SQL Tools Version

      In some cases, users may download SQL Tools or the Compare Bundle of one version, but when installed, the individual tool versions do not match the version of the downloaded package. The reason for this is that SQL Tools is essentially a bundle ...

    • Limit of activations exceeded (dbForge)

      The point is that when you change any hardware part of your computer or reinstall the OS or change a profile on your computer, your Hardware ID changes so the software considers it as an installation on an alternative computer. Virtual machine ...