Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 how to raise remote login timeout (s)

Author  Topic 

Hommer
Aged Yak Warrior

808 Posts

Posted - 2007-02-22 : 16:16:48
Hi, all,

How to raise remote login timeout (s)? (I know sp_configure will do, but am not sure it is the way to do on production server)
And is it a good practice to do so?
I have it at 20 sec. I assume that is the default.

Thanks!

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-02-22 : 16:37:49
How is the user logging into the system? From a front-end application? From Enterprise Manager? From Query Analyzer? ...

Tara Kizer
Go to Top of Page

Hommer
Aged Yak Warrior

808 Posts

Posted - 2007-02-22 : 16:59:17
From front end in Access 97. In there I have raised the command timeout and connection time out.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-02-22 : 17:37:05
Connection timeout is what you would need to modify.

Command timeout is for queries. Connection timeout is for connections to the server. We typically set the connection timeout low as if it can't connect within a short amount of time, then there's a problem. Command timeout we start at 30 and then move up as necessary (due to bad queries or poor db design).

Tara Kizer
Go to Top of Page

Hommer
Aged Yak Warrior

808 Posts

Posted - 2007-02-23 : 08:57:44
I have moved the connection timeout up. For now, at least for testing, I have it to 0, which is indefinite, but I still get timeout. That sp takes 5 to 10 minutes if it is in the sql QA.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-02-26 : 13:07:59
quote:
Originally posted by Hommer

I have moved the connection timeout up. For now, at least for testing, I have it to 0, which is indefinite, but I still get timeout. That sp takes 5 to 10 minutes if it is in the sql QA.




But are you getting the timeout on the connection to SQL Server or on the query? These are two separate things. The fact that you mention that the stored procedure is taking 5 to 10 minutes in QA leads me to believe that you are wanting to increase the command timeout.

Tara Kizer
Go to Top of Page
   

- Advertisement -