SQL Clone 4

In SSMS, 'The connection is broken and recovery is not possible' error is seen after a clone is deleted

This error can occur when a clone that you've recently accessed in SSMS is deleted by a Clone agent.

You can work around this issue by setting an additional connection parameter when connecting to your instance.

In that pane, add the following:

ConnectRetryCount=0;

This value is cached by SSMS per-instance, so connections to other instances won't be affected, and you should only need to enter it once.


Didn't find what you were looking for?