Daily Archives: October 4, 2010

Participate in #TSQL2sDay

Posted on by
Reply

Sankar Reddy has blogged about what will be discussed as next topic: Misconceptions in SQL Server.
TSQL2sDay150x150

What is SQL Tuesday? As he explains, it is the opportunity for the community to improve based on a topic chosen about SQL Server. It happens every 2nd Tuesday of each month; an original idea from Adam Machanic.

These are the rules:

1. Your post should go live between 10/12/2010 00:00:00.000 GMT (2nd Tuesday) and 10/13/2010 00:00:00.000 GMT.
2. Your blog post has to link back to the hosting blog, and the link must be anchored from the logo (found above) which must also appear at the top of the post.
3. If trackbacks won’t work properly then please leave a comment below so that your post is accounted for in the roundup.

Get involved.

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

Posted on by
Reply

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.