How can we help you today? How can we help you today?
SCrouchman
So, its definitely SQLPrompt & SQLSourceControl thats causing the issue, with SQLPrompt being the biggest offender. Steps followed for each test Make sure SSMS is closed Move an extension back into the correct folder Open SSMS Connect to VPN Connect to Server in SSMS Disconnect from VPN Connect to local Server in SSMS (via object explorer) Disconnect from Server from step 5 With SQLSourceControl I can connect and interact with my local Server fine, but loading the context menu to disconnect from the other server locks up SSMS. However it does eventually load and I can keep opening the context menu with no issues. Trying to right click on any of the databases on that server does the same thing With SQLPrompt I can't even connect to my local server, it locks up immediately when I try to click anywhere in Object explorer. It does eventually respond and I can connect to my local server, but if I disconnect and try to reconnect same issue again. Also whenever I try to interact with the original server in anyway it locks up, this means if I right click to disconnect it will hang before showing the context menu, and often the menu will disappear when it becomes responsive again and I have to force quit ssms. Hope this helps, happy to try anything here. I could probably live without SQLSourceControl as only one of our systems uses that, but SQLPrompt is the main reason for having the toolbelt installed / comments
So, its definitely SQLPrompt & SQLSourceControl thats causing the issue, with SQLPrompt being the biggest offender.Steps followed for each test Make sure SSMS is closed Move an extension back into ...
0 votes