Old-Dog
asked on
Sql Timeout
ODBC--update on a linked table 'table name' failed
[microsoft][odbc sql server driver]timeout expired(#0)
This occurs on Workstations and on the server.
Server is server 2008Fundamenta R2
Sql is 2008
[microsoft][odbc sql server driver]timeout expired(#0)
This occurs on Workstations and on the server.
Server is server 2008Fundamenta R2
Sql is 2008
Give this question and its answer a review:
https://www.experts-exchange.com/questions/20780672/Microsoft-ODBC-SQL-Server-Driver-Timeout-expired.html
https://www.experts-exchange.com/questions/20780672/Microsoft-ODBC-SQL-Server-Driver-Timeout-expired.html
ASKER
Yes, it was working, for several months. Nothing changed in the front end app (MsAccess03) or in SQL. To my knowledge. It is in the Windows 2000 area beacuase I screwed up. OS on Server is 2008, SQL is 2008. Workstations are XP Pro. It is a very small domain and database is also fairly small. The problem seems (keyword) more prevalent when multiple updates are done.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check if that would help you..
http://www.sqlservercentral.com/Forums/Topic166248-131-1.aspx
http://www.sqlservercentral.com/Forums/Topic166248-131-1.aspx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Query on linked server? Sounds like something I know!
Okay if the linked server is an SQL server, then the most likely issue is RPC timeout set on the remote server.
Go to server properties on the remote (linked) server, check remote connection settings and change the remote query timeout by increasing it to what you want - like 5 hours.
I've once suffered from the same issue & resolved it that way.
If the linked server is another platform like Oracle, Informix, then the issue is different.
Regards,
Chris.
Okay if the linked server is an SQL server, then the most likely issue is RPC timeout set on the remote server.
Go to server properties on the remote (linked) server, check remote connection settings and change the remote query timeout by increasing it to what you want - like 5 hours.
I've once suffered from the same issue & resolved it that way.
If the linked server is another platform like Oracle, Informix, then the issue is different.
Regards,
Chris.
By default, SQL server limits remote queries to 600 seconds
ASKER
Thanks
If so, what has changed in the interim?
You have this question in thw Windows 2000 OS area - how does Windows 2000 play in this?