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.
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.
In the past we used the very reliable RedGate software to compare database schemas and create scripts for production push. Not always a copy paste, but a good reference for the DBA team to understand the changes and customize/enhance the scripts. We opted to work with OpenDBDIff but broke once we moved to Windows 7 X64. Now there is a version that seems to be working properly on X64 Windows.
Over 3 weeks ago we solved the issue we were having with one particular cluster node running SQL Server 2008 R2. We have been going back and forth with Microsoft to obtain an explanation on why the erratic behavior of the RDBMS engine.
We migrated from SQL Server 2005 X86 to SQL Server 2008 R2 X64 a couple of weeks ago. The new hardware has twice as much RAM, much better I/O and CPU power to spare. I have discussed about the first issues we encountered with Hyper-Threading enabled here.
I want to share a note about our latest experiences with SQL Server 2008 R2 EE X64 and Nehalem Processors. We have an active/active SQL Server cluster solution running on Two Dell R710 machines and Equallogic Storage Solution using iSCSI. Each Server has Two Intel X5550 processors, 64 GB of RAM and is running under Windows Server 2008 R2 EE X64.