At present, if I developed a SQL query, stored it and try to load it back into dbForge at a later date, dbForge 'remembers' the SQL connection it is associated with and tries to connect automatically. I want to be able to disable this behaviour via options - eg opening file does NOT try to be clever.

EXTENDED RATIONALE

In common usage, the feature is quite useful. Unfortunately, in some of the projects I am working with, I have to constantly switch between different environments (prod, pre-prod, demo, devops, etc) protected by external VPN. All environments are hosting the same databases, but, due to security, I could only be connected to one environment (and hence one particular database) at a time.

It is common for me to use the same stored SQL (after all, all environments contains essentially the same schema). But right now, if I open SQL script which was previously executed in a different environment, dbForge freezes while it tries to connect (which it cannot), which is annoying and time wasting.

To be clear - I do NOT want to get rid of existing functionality - it remains highly useful in some projects. But I want to be able to control it via Options or Settings, to be able to switch it on and off, as needed.