SSMS stops responding when visual studio is running in parallel on same machine

Question

Hi- I am facing an issue in SSMS. Every time a visual studio(2017) instance is running on the same machine, SSMS (SQL Server 2016) stops responding on any action like 'new query' 'right click on a table' etc.
As soon as I close visual studio, SSMS resumes working.
This does not allow me to work with these two applications running in parallel at any point in time.
Anyone faced such issue, any leads will be appreciated.

Answer 1

Hi gaupop-4423，

Maybe you can check your error log to see if there are errors prompted?
Did you install VS 2017 first?
SSMS 2016 will use Visual Studio 2015 Shell (Isolated) as background. If you have installed Visual Studio 2017, there will be some conflict when you install Visual Studio 2015 Shell (Isolated).

So, you can try to uninstall VS 2017, then intall SSMS 2016 first and then reinstall Visual Studio 2017

-------------

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

That is SSMS 16, the first version of SSMS to ship separately from SQL Server. And a fairly early version of it. Why it would clash with VS 2017, I don't know.

But in any case, I think the best way to resolve this is to download and install the most recent version of SSMS, which is 18.10: https://learn.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms. If you don't have permissions to run installations yourself, request an administrator to make the installation.

Note that this is not an upgrade, but SSMS 18 will be installed side-by-side with SSMS 16.

Answer 3

Hi All.. I requested physical memory upgrade to the server and it seemed to have helped this. The reason for increase in RAM was whenever SSMS stopped responding, the memory utilization was at peak (98%). So far the applications are working fine simultaneously after the upgrade. Thanks for all your inputs.