SQL 2008 server CPU gets 100% if it goes above 300 sql connections.
Usually we running about 180-200 SQL connections without issues at 20% CPU. Occasionally it reaches 300-500 sql connections and CPU just pegs to 100%.
So far looks like legit traffic, all legit connections on sql from our Webservers.
Any suggestions what to look at on SQL? It should definitely handle that many connections, its not really that many of them, so if with 200 connections running at 20% with 400 should be running around 40% im thinking.
Any suggestions greatly appreciated,