I have an ASP.NET 4 project using SQL Server 2016 on Windows Server 2012. This is the environment for me as a single user. When I run the project in IIS8 and use Visual Studio 2015 Debug → "Attach to Process", it connects perfectly to my w3wp process. However, in the task manager, I can immediately see that the process "SQL Server Windows NT - 64 bit" jumps to CPU usage by 20% even in harsh conditions. I repeated this several times, and it is definitely related to VS debugging. When I stop debugging, it returns to 0% for a couple of seconds, but then returns to 20% and stays there.
The problem is that even trivial SQL queries are terribly slow or time out in this state. Thus, debugging or even opening any supported DB project page becomes almost impossible.
The only way to facilitate SQL-Server and reuse the site is to close the entire solution in Visual Studio.
Is Visual Studio launching some (unwanted!) Hidden SQL debugging when running general debugging? If so, how can I disable this?
source share