Re: Reconnect does not work TADOconnection
- From: "Steve Zimmelman" <skz@xxxxxxxxxxxxxxxxxx>
- Date: Tue, 4 Mar 2008 16:16:01 -0500
Sorry, I didn't read your last post entirely. Here's the code.
http://skzimmelman.com/Articles/skzADOConnKeepAlive.html
A timer is set to enabled after the connection processess a command, and
disabled when a new command is started. So the ping should only be executed
after a set period of inactivity. In our case, 5 minutes seems to work
well.
The code that is used to "ping" is:
Execute('Exec sp_server_info 1',i,[eoExecuteNoRecords]);
So it shouldn't take too much bandwidth to test.
-Steve-
"Ron J" <rjohnson@xxxxxxxxxxxx> wrote in message
news:47cd8336@xxxxxxxxxxxxxxxxxxxxxxxxx
Thanks Steve. 'ping' sounds like a good idea - I'll try it.
Funny thing for us is we have had this application on SQL2000 for 4 years
(400 users) and 1 or 2 of these drops per week. We upgraded the servers
(to Core2 x 2, SAN, SQL2005, 64bit W2K3) and we get about 100 per day (out
of 400 users). Some users are remote over T1 so they are really hot when
they have to restart the app (load time is 90 seconds over T1). [We are
porting to Web now]
On your timed ping, how often are you pinging the server to keep it
active? What kind of 'ping'? Just any simple short Select to do something?
Thanks,
Ron
.
- References:
- Re: Reconnect does not work TADOconnection
- From: Steve Zimmelman
- Re: Reconnect does not work TADOconnection
- From: Ron J
- Re: Reconnect does not work TADOconnection
- Prev by Date: Re: Reconnect does not work TADOconnection
- Next by Date: Re: Deleting a record
- Previous by thread: Re: Reconnect does not work TADOconnection
- Next by thread: TADOStoredProc problem
- Index(es):
Relevant Pages
|
