SQL Trace causing error “The client was unable to reuse a session with SPID XXX”

We will open traces whenever a slow performing process needs to be pinpointed. We never experienced a high overhead until today.

A couple of our production sites and services started to time out and SQL Server started login this errror:

From: SQLAlerts [mailto:[email protected]]
Sent: Monday, October 04, 2010 10:13 AM
To: [email protected]
Subject: SQL Server Alert System: ‘Severity 020’ occurred on \\XYZ

DATE/TIME:        10/4/2010 10:12:41 AM

DESCRIPTION:   The client was unable to reuse a session with SPID 345, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

COMMENT:        (None)

JOB RUN:             (None)

We stopped the trace and everything went back to normal. The trace was being stored to a file.

Is the overhead that high to cause these kind of errors? We’ll try to figure it out.

The 2011 Volvo S60. “Get Naughty” Event

Yesterday I went to the “Get Naughty” event and test drove the 2011 Volvo S60. A great car overall, with a nice interior, enough horsepower and great looks. Not as big as the S80 and a bit expensive with options (north of 40K loaded). I will wait for the R-Design to arrive and consider the European Delivery Program. I have owned 4 Volvo’s so far and they were all great, including the latest ’10 Volvo XC90 R-Design. The BMW 328i and Audi A4 were also available for a test drive. I can say that the interior of the BMW is awesome, but the engine did not deliver. The Audi looked outdated and I did not have fun with its Turbo lag. But again, I am biased as I tend to chose Volvo anyways.

Took some pictures while at the event:

The wife testing the “Pedestrian Detection” option.