Odbc Timeout Error Sql Server 2000
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about
[microsoft][odbc Sql Server Driver]timeout Expired
Stack Overflow the company Business Learn more about hiring developers or posting ads with odbc sql server driver query timeout expired #0 us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is increase odbc timeout a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Intermittent SQL Server ODBC Timeout expired up vote 3 down vote favorite We have
80040e31
a bunch of VB6 applications that access two different database servers (both 32-bit windows 2003, one SQL Server 2000, one SQL Server 2005). About every ten minutes or so, we are getting a few errors: [Microsoft][ODBC SQL Server Driver]Timeout expired [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. [Microsoft][ODBC SQL Server Driver]ConnectionRead() This is happening on more than a dozen different computers at random times. We also
Odbc Connection Timeout
have IP phones that all run through the same network and those are not having any problems. We can also VNC into a users computer and reproduce the error they were getting, but VNC still continues to work. Email also works. It just seems to be an ODBC connection to SQL Server that causes the issue. The errors happen for both of our SQL Servers. We have scoured google, but haven't been able to come up with a solution. Is there anything we can try to diagnose the problem? Is there any fix out there? Update: We have no internal firewalls on either the servers or clients. We connect through TCP/IP via the dns name of the server (also have tried IP address). One server has Windows 2003 SP2 and the other doesn't. The strange thing is that it has worked fine for years and now all of a sudden these errors are happening. Nothing has changed on those servers for quite some time. That leads us to beleive it is a bad switch, but that seems unlikely since nothing else (email, phones, vnc, file server, etc) all work without problems. sql-server vb6 odbc share|improve this question edited May 23 '11 at 12:44 Bill the Lizard 223k139448737 asked Dec
picture album Shortcut keys My code library VB resources SQLServer resources SQLServer books Replication FAQ Scripting resources ASP resources Search my site Sign my guestbook Contact information SQL Server Articles New NEW!!! Subscribe to my newsletter: Want to keep in touch with the latest in SQL Server world? Email vyaskn@hotmail.com with 'subscribe' in the subject line See also: Database coding conventions SQL Server interview questions Evaluation of federated database servers SQL Server FAQ on programming, administration, replication and tools SQL Server security best practices SQL Server administration best practices Related books: How to troubleshoot ODBC timeout errors experienced by applications accessing SQL Server? There are a lot of reasons why one ends up with http://stackoverflow.com/questions/378881/intermittent-sql-server-odbc-timeout-expired a timeout error. This article discusses the most common reasons that result in timeouts. For more specific information on handling timeouts, along with code samples, read the article: DBA's Quick Guide to Timeouts By default, ADO connections time out after 30 seconds. So, your query or stored procedure is obviously taking more than 30 seconds to complete. You can verify this by running your query/stored procedure in Query Analyzer and noting the execution time. You can also use Profiler http://vyaskn.tripod.com/sql_odbc_timeout_expired.htm to see the execution time of queries (Start time, End time and Duration columns in Profiler). Once you confirm that the query indeed is taking more than 30 seconds, find out why it is taking more than 30 seconds and see if you can tune it to make it quicker. The most obvious step is to look at the Execution plan in Query Analyzer. Any table scans are bad. Make sure you have right indexes on your tables, and that the query is written in an efficient way and is using those indexes (Index seeks are preferred). If you are not sure, how to tune indexes, try the Index Tuning Wizard. Btw, if you are using cursors, see if the query can be rewritten without using a cursor. Cursors make things slow. Consider that indexing is fine, but still the query is slow. Few things to look at: Is your query doing clustered index scan, and the index is fragmented? If so, you need to rebuild the index using DBCC DBREINDEX or DBCC INDEXDEFRAG (in SQL Server 2000 only). I rebuild indexes on some of my tables evrey weekend using a scheduled job. Assume that there is no fragmentation in the index. Next thing to verify would be to see if there is any blocking going on. Use the system stored procedures sp_who or sp_who2 (undocumented, but provides more info, compared to sp_who) to verify blo
0 Hello all, Happy new year!!! we are having few sql2000 instances. Recently we are facing the connection timeouts and all the applications connecting to SQL Server are getting hanged. After https://ask.sqlservercentral.com/questions/97164/connection-timeouts-in-sql-server-200.html the server restart, everything seems normal.. only thing i got from the cient team is ... [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00] [165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00] [382] Logon to server '(local)' failed (JobManager) [298] SQLServer Error: 11, General network error. Check your network documentation. [SQLSTATE 08001] what might be the cause ?? may I please How to sql server dig into this issue ? more ▼ 1 total comment 616 characters / 98 words asked Jan 01, 2013 at 05:09 PM in Default rammy 20 ● 1 ● 1 ● 2 edited Jan 01, 2013 at 05:12 PM Is there anything in the windows event log? Jan 01, 2013 at 07:08 PM ThomasRushton ♦♦ add new comment (comments are locked) 10|1200 characters odbc sql server needed characters left ▼ Everyone Moderators Original poster and moderators Other... Viewable by all users 1 answer: sort voted first ▼ oldest newest voted first 0 There could be a number of different causes. It could be resource related. Meaning a process, or processes, used up all the resources, such as memory, preventing further connections. You'll have a hard time tracking this down after the fact. You need to check what resources are being used by which processes and if that is causing excessive blocking or delays by using sp_who2 at the time of the issue. If not that, then it's possible it's something to do with the OS or with hardware. As @ThomasRushton says, check the windows events log for errors as a starting point. more ▼ 0 total comments 572 characters / 100 words answered Jan 02, 2013 at 11:18 AM Grant Fritchey ♦♦ 137k ● 20 ● 43 ● 81 add new comment (comments are locked) 10|1200 characters needed characters left ▼ Everyone Moderators Original poster and moderators Other... Viewable by all users Your answer toggle preview: Attachments: Up to 2 attachments (including ima