July 31, 2011 at 10:53 pm
I'm having a problem with a production server, SQL2008R2 10.50.1600 RTM.
30 or so databases, very busy, running on a Windows2008 Server R2.
Over the past few weeks, users have reported connection timeout from multiple applications. I've just received the same error from SQL management studio 2008R2 CU7, however it is nearly impossible to replicate the issue.
Error details:
I have a short outage window tomorrow, to disable logging of successful logins (there are a couple of web apps with connection pooling causing a huge amount of successul logins going to the log), however, what else could I check for during the outage window?
August 2, 2011 at 8:30 am
There is a HUGE range of potential causes for the issues you are seeing. Best bet is to get a professional tuner on board to give your systems a review. You can use the free sp_whoisactive to see perf and blocking issues.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
August 2, 2011 at 8:37 am
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply