Re: SQL server 2000 timeout
- From: "Madhivanan" <madhivanan2001@xxxxxxxxx>
- Date: 5 Jul 2006 06:29:32 -0700
http://vyaskn.tripod.com/watch_your_timeouts.htm
http://vyaskn.tripod.com/sql_odbc_timeout_expired.htm
Madhivanan
Cimode wrote:
You need to do some tuning...
Erland Sommarskog wrote:
Brad (bmeyynospamnospam@xxxxxxxxxxxx) writes:It is controllable through EM...Server Property box --> connexions tab
I have been trying to do a query(view) in Enterprise Manger and Query
Analyzer with a timeout result everytime. In EM in happens in about
30 seconds and in QA it happens in about 45 seconds.
I don't think the timeout in Enterprise Manager is controllable.
-->Request timeout in ms...
In Query Analyzer you set it under Tools->Options->Connection->Query Timeout
(in seconds). By default it's 0, which means forever, so you would only
get a timeout if someone has changed it.
If the view refers to remote tables, you could get a timeout for the
remote part of the view, but this timeout is by default 10 minutes.
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- SQL server 2000 timeout
- From: Brad
- Re: SQL server 2000 timeout
- From: Erland Sommarskog
- Re: SQL server 2000 timeout
- From: Cimode
- SQL server 2000 timeout
- Prev by Date: Re: comma separated values to stored procedures
- Next by Date: need programmer to build a dts...
- Previous by thread: Re: SQL server 2000 timeout
- Next by thread: Announcing Yellowfin Version 2.5 release for SQL server based users
- Index(es):
Relevant Pages
|
Loading