We've got 7.0 running on NT 4.0 and we're running into a problem where it
appears the users are hitting a web page that submits a query to the db and
then get impatient - so they hit the stop button on the browser. We're
using the MS jdbc driver to hit SQL Server from Java Servlets and all of
the web processes seem to handle this fairly cleanly, but on the db machine
we zoom from using 3% of the cpus (dual cpu box) to using 50% or better.
Needless to say everything slows quite a bit at that point. Interestingly
enough there is no disk activity going on so it's not as if SQL Server is
working like mad through some series of large tables. Anyone else heard of
anything like this? If so does moving to SQL 2000 and applying the service
packs help? Came across a few articles in the knowledge base that showwed
sql serevr going into an ifinite loop for other conditions and in several
of the cases the answer was to get to SQL 2000 with sp 2, but I'd like to
get some comments from anyone in the field that has faced this before we go
spend the money.