Re: DBPROB for Session timeout
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Sat, 28 Apr 2007 21:13:15 +0000 (UTC)
Frank (Frank@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
I am aware of three timeout-PropVals:
1. DBPROP_INIT_GENERALTIMEOUT
2. DBPROP_COMMANDTIMEOUT
3. DBPROP_INIT_TIMEOUT
Which one of these values sets the timeout for a SQLServer-Session? The
problem I am facing: I am using SQLExpress with my application on the same
computer (*not* remote). When the computer goes into sleep-mode and then
wakes-up a few hours later the session has expired.
Error report as follows:
Microsoft OLE DB Provider for SQL Server
Description: Timeout expired
GUID: {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}
I don't know which of the timeouts that is, but whichever, I don't think
you want to make it longer. That is, what happens is that when the machine
goes to sleep, the connection is severed. Your application is not aware
of that, and first command it issues stalls, and when there is no reply
spon the other end, it eventually produces the message.
If you have SQL Server Mangement Studio, Express or "big" version,
installed, you can test this by open a query window, put the computer
to sleep, and then when it wakes up, the window will say "not connected".
--
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
.
- Prev by Date: Re: SQLOLEDB always uses Named Pipes
- Next by Date: Re: DBPROB for Session timeout
- Previous by thread: polling a database
- Next by thread: Re: DBPROB for Session timeout
- Index(es):
Relevant Pages
|
Loading