[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 770
  • Last Modified:

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
0
Old-Dog
Asked:
Old-Dog
  • 3
  • 2
  • 2
  • +3
3 Solutions
 
dew_associatesCommented:
Did you have this working originally?

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?
0
 
dew_associatesCommented:
0
 
Old-DogAuthor Commented:
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.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
dew_associatesCommented:
Try increasing the ODBC timeout from 60 to 180
0
 
QlemoC++ DeveloperCommented:
Timeouts in MSSQL originate from either locking issues (need to wait for releasing of aquired row locks) or execution time issues. If your query just runs too slow, because there are no indexes for example, you will get the same message. From your description I cannot tell which one it is, but SQL Profiler (or Activity Monitor, when online) could. Profiler needs to be set up to only display queries lasting longer than let's say 30 seconds, and/or locks aquired and released. The latter might result in heavy logging.
0
 
Jason Yousef, MSSr. BI DeveloperCommented:
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Concurrency queries can hangs for some reasons. Usually it's because the query return a big amount of data or query don't use indexes. So depending in the reason you can have differente solutions but it's always a good idea to check indexes and statistics to see if they are used and up to date. You can also use locking hints but for now my advice is to avoid this by now.

Good luck
0
 
Chris MConsulting - Technology ServicesCommented:
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.
0
 
Chris MConsulting - Technology ServicesCommented:
By default, SQL server limits remote queries to 600 seconds
0
 
Old-DogAuthor Commented:
Thanks
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 3
  • 2
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now