December 28, 2011 at 11:57 am
After migrating to SQL 2008 from SQL 2005 we are getting random Time out expired errors.
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
We do not have the problem on our older SQL 2005 servers, or on our test SQL 2008 servers. We only receive this on our production SQL2008 servers.
Has anyone else run into this problem?
Our application is a VB.net with the 3.5 dot net framework.
December 28, 2011 at 12:08 pm
Since it is only occuring on your production db servers make sure that the TCP/IP port for the Database Engine instance is not blocked by a firewall. Also what port is SQL Server listening on? Has that possibly changed lately? Also check to see if the SQL Server Browser service is running but Port 1434 is not blocked by a firewall. All of these and more can cause these timeouts to occur. I would check these first. 😀
"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"
December 28, 2011 at 12:15 pm
I dont think its a firewall issue. The timeouts are random (as far as we can tell). During the day we may get 50 to 100 transactions that timeout, but we get thousands that work just fine.
Some of the transactions that timeout are very simple queries that return very little data. Also, we are NOT seeing any blocking issues.
December 28, 2011 at 12:17 pm
Is this error being caught by the calling vb.net application? Are you positive nothing on that side has been changed? Are you on different hardware now?
December 28, 2011 at 12:31 pm
Yes, its being caught by our application. Yes we are on new hardware. We moved SQL and our applications to Windows Servers 2008 from Windows servers 2003.
December 28, 2011 at 12:38 pm
I'm no applications developer but I do know their is usually a configurable timeout period specified in the calling app. It sounds like you're hitting that threshold now. Probably because of the new hardware. You're probably not getting the same level of performance that you were on the old hardware. If you moved to a server with more CPUs you may be having problems with parallelism. I've never experienced that before but I'll try and find a post that I saw about that some time ago.
December 28, 2011 at 12:54 pm
Couldn't find the article that I was thinking of. Anyways, it could be a couple other things as well. I would check memory configurations, make sure statistics are up to date, and check execution plans between both versions.
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply