SQL Server Performance Forum – Threads Archive

help – timeout errors

Hi Since last Thursday we have been suddenly getting lots of timeout errors when using Enterprise Manager and Query Analyser. It happens about 80% of the time. I don’t know what is causing them or why they have suddenly started. All the people that are getting the problems are remote to the server and have to go across a network to retrieve data. The network connection appears to be fine as other network things works. Also in programs that use the database we are getting timeout errors and the programs are taking a long time to retrieve data from the database. The problem gets worse if the user is also using Enterprise Manager. We have tried installing SP4 (for SQL server 2000) but this has not stopped the errors from occuring. I can’t think of anything else to try so any suggestions would be much appreciated. Thanks CE

Recall what kind of changes happened in the infrastructure, such as hotfix or service pack application to any of the servers that are involved in this application service. Also check the execution of scheduled jobs and database maintenance jobs that can take care of optimum performance. Its good to perform UPDATE STATISTICS and RECOMPILE extensively used indexes & stored procedures. http://vyaskn.tripod.com/sql_odbc_timeout_expired.htm fyi. Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Hi Nothing has changed on the server, also the timeout error occurs when you try and connect to another server that is also running SQL server 2000. All the statistics are uptodate etc. It appears that the problem occurs when running VB or ADO (programming in VB and also running compiled programs) AND enterprise manager or Query Analyser at the same time. If you use only EM or VB then everything works fine but as soon as you run the two together you get time out errors. Once you have run the two together then after this time if you try using VB or EM by itself again then it still timeouts. Our other DBA does not use VB or any of the programs that use ADO and he can’t replicate the error at all on his PC. However, it occurs on my PC about 80% of the time. Has anyone heard of this happening before? CE

Try recompiling the stored procedures, triggers and reindex the heavy indexes and monitor the timeouts. A good guide tohttp://vyaskn.tripod.com/watch_your_timeouts.htm watch timeout. Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

]]>