Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm having the problems described in KB937745 - very high CPU usage and the Application Log is reporting something like this:

The client was unable to reuse a session with SPID SPID, which had been reset for connection pooling. 

I've downloaded the hotfixes and I can't run them - I suspect it is because SQL Server 2005 Express Edition is not in the "Applies to" section of the KB:

alt text

The machine is running on an ESX 3.5 host running Windows XP (patched).

Result of:

SELECT  SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')


9.00.3068.00    SP2 Express Edition

Any ideas? I'm stumped why the CPU is getting pegged. This is a product from a vendor that has never seen this kind of problem with several installations.

share|improve this question

migrated from May 6 '12 at 18:27

This question came from our site for professional and enthusiast programmers.

I'm working with a virtualised dev server that's got I/O performance problems as well. Watching with interest to see if something comes of this. – ConcernedOfTunbridgeWells Nov 12 '08 at 20:26
I don't think it's an IO problem. We run several production systems with high IO in our virtual environment, including SQL Server systems. – andyh_ky Nov 12 '08 at 21:11
up vote 4 down vote accepted

I found an article that might be of help.

Edit: The link above is now dead, but the Wayback Machine has a copy here.

The blog post states that

Finally we have identified the root cause of the issue is due to the activity on the database causing heavy usage of MARS [Multiple Active Result Sets]

which was a feature introduced in SQL Server 2005 (ref: here).

share|improve this answer
Shockingly, it is a problem with our vendor's application. This link helped me track down the problem. – andyh_ky Nov 14 '08 at 14:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.