Autocomplete Cache Is Lost or Not Populated When Switching VPN or Reconnecting to a Server
Autocomplete suggestions for database objects, including tables, columns, and stored procedures, may stop appearing after switching a VPN connection or reconnecting to a SQL Server instance. In some cases, suggestions become available only after the cache is rebuilt; in others, autocomplete may remain incomplete until a manual refresh is performed.
Root Cause
SQL Complete builds the object cache incrementally. Initially, only basic metadata is loaded, while additional objects are fetched on demand as they are accessed.
The cache is persisted locally between sessions. However, if SQL Complete attempts to retrieve additional metadata while the connection to the server is unavailable (for example, during a VPN switch or a temporary network interruption), the requested objects cannot be loaded and therefore are not added to the cache. From the user's perspective, this may appear as if the cache has been reset or partially lost.
It is important to note that the cache is replaced only after a successful refresh operation. Therefore, an interrupted refresh process should not result in the loss of metadata that has already been loaded.
Workaround
To prevent the cache from being refreshed automatically, disable the corresponding options in SQL Complete:
- Open SQL Complete → Options → Suggestion → Refresh.
- Clear the following checkboxes:
- Automatically refresh local cache every
- Detect changes on a server before refreshing local cache
With these options disabled, the cache remains available throughout the current SSMS session and is no longer overwritten automatically. If the database schema changes, the cache can be refreshed manually by pressing Ctrl+R.
Product Limitation
Persisting the complete object cache for each database across SSMS sessions is not currently supported. This functionality is planned for implementation in future versions of SQL Complete.
Related Articles
Lost Connection to MySQL Server
A lost connection to a MySQL server is a common issue and, in most cases, is not related to dbForge tools. It typically occurs due to server settings, network interruptions, or long-running queries. Recommended Solution For official guidance on ...How to Connect to MySQL Server
In the second article of the series uncovering how to get started with MySQL, we talk about the ways of connecting to MySQL Server. You can connect to MySQL Server using MySQL Client, dbForge Studio for MySQL, and MySQL Workbench. In this article, we ...How to Use an MCP Server in Your AI Tool to Search Devart Documentation
Devart provides an MCP (Model Context Protocol) server that connects your AI tool directly to our full product documentation. Instead of switching tabs and searching manually, you can ask questions in plain language and get precise, context-aware ...Assembly version is found in Global Assembly Cache
The issue can occur if gacutil left an empty folder in the \GAC_MSIL\ after uninstalling a previous version of a dotConnect provider. This is a very rare case in fact. The Global Assembly Cache can be found here: ...Resolving Assembly Version Issues by Cleaning the Global Assembly Cache (GAC)
You might encounter assembly version conflicts if an incomplete uninstall of a previous dotConnect provider leaves an empty folder in the Global Assembly Cache (GAC). This is an uncommon occurrence. Accessing the Global Assembly Cache: The Global ...