0

Having a major issues with this procedure called SP_ExecuteSQL;1.

It keeps executing internally in SQL Server 2000 with high utilization of CPU. When I pass its SPID in DBCC inputbuffer it shows as internal.

Is there any way of stopping it?

  • Have you restarted the server or services? – Shawn Melton Dec 27 '14 at 14:37
  • Have you run a server-side trace to see what is being executed and where it's coming from? You can't stop something if you don't know what it is. Also how exactly do you know that this is the cause for your high CPU? – Aaron Bertrand Dec 27 '14 at 15:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.