I am having one hard time trying to figure this out... I have a website that is getting timeout errors at random. The wierd problem is that it is only going on with this one site. Other sites (but on different servers) have no problem's ever connecting to the SQL Server. I have added in the code to email me with the status of any SQL errors in all different sites accessing the same SQL Server and only get this error from one server. In my opinion it has to be a network issue but would like to try and figure it out so seeing what else I can do to find out if it is a network problem.
Should I set it up so it is always pinging the IP Address of the SQL Server to see if it's ever not able to ping the server then I know its a network issue instead of anything else?
Windows 2000 and yes it is intermittent.. when I get to my other computer I can post all the times it has happened. I do not want to have to change the timeout but will just to get it to always work. Basically I think there has to be something on the network that is causing it to happen.
It is not a heavy query.. it could be on a page that usually takes .3 seconds to load and i know its not because the sql server is overwhelmed because other high traffic sites on other servers never have this problem
The MS suggested way of connectiing to a SQL server is not by IP, but by server name with a coresponding entry in the host file.
I don't believe that's the problem though. I'd guess network. If it's on the same network as the others, then maybe a faulty card/connection, some errant service spewing packets or a service trying to contact a dead IP and using up the sockets while waiting for an ACK.
I am using a external IP Address. I put a server on a different class C to hopefully help on a few things I am doing but is all inside the same data center.
Topic Locked
Posted - 05 January 2005 : 10:58:50
