Re: Wireless ADOConnection
- From: "Kevin Frevert" <kevin@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 8 May 2008 13:34:51 -0500
"autumnSouth" <autumnsouth@xxxxxxxxxxxx> wrote in message
news:48231bc4$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Delphi 2007 for Win32 + MSSQL 2005 + Adoconnection (StayConnect is true)
we have a client application connected to SQL 2005 server using
Adoconnection + wireless network. The application disconnected from server
around every 5 mins and need restart to reconnect.
Ay suggestions on what's happening? StayConnect is true, and we have very
large timeout value.
That is part of the problem. There is no way for the TADOConnection to know
that it lost the database connection. One workaround is to set the
StayConnected property to false and re-connect for every transaction. ADO
connection pooling *should* help with re-connection performance.
Others have successfully created a background thread that 'pings' the server
(a simple Select GetDate() will do) and if the app cannot connect to the
database, it closes the connection and re-connects. If you have a lot of
wireless units, this may not be a viable solution (the DBA will be paying
you a visit :)
Take a look at http://www.fulltextsearch.com and search on ADO wireless,
lost connection, etc. Sorry, I couldn't find the thread with the example of
a TADOConnection descendent that performed the 'am I still connected?'
check, but I know it's there somewhere.
Good luck,
krf
.
- References:
- Wireless ADOConnection
- From: autumnSouth
- Wireless ADOConnection
- Prev by Date: Wireless ADOConnection
- Next by Date: Re: Help optimize Dataset copy code
- Previous by thread: Wireless ADOConnection
- Next by thread: Re: Help optimize Dataset copy code
- Index(es):
Relevant Pages
|
