Preserving connection

From: Sander Verhagen (Verhagen_at_nonono.Sander.com)
Date: 07/23/04 

Date: Fri, 23 Jul 2004 11:55:19 +0200

Hi,

I have a VC++ application that through ADO connects with a SQL Server. The
SQL Server instance will, in many cases, be running on a different machine.
We envision that different machine often to be very distant and connected
through a VPN connection. All together I can't assume my database connection
to be there "forever" after I've created it on instantiating my application.
I could connect and disconnect surrounding each r/w action with the
database, but that sounds awfully heavy.

Most database connection implementations that I've had the chance to look
at, recently, seem to assume the database to be there forever, e.g. on the
same machine.

Could anyone tell me about or point me to an explanation on best practices
in this matter? The matter, once more perhaps, is that I want to have a way
to preserve a reliable connection to the database from my business logic's
point of view... how do I implement that in an ADO based database tier?

Thanks already,

Sander Verhagen
[ Verhagen@nonono.Sander.com ]

Relevant Pages

  • Re: ADO Connection Timeout
    ... so what happens when a connection failure forces one station to revert ... to a local database? ... Further, you *will* have contention issues, Jet does not support record ... to the central server, but you are willing to live with periods where it ...
    (microsoft.public.data.ado)
  • Re: ADO Connection Timeout
    ... When the first test is run, the results are stored in the central database. ... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
    (microsoft.public.data.ado)
  • Re: ADO Connection Timeout
    ... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
    (microsoft.public.data.ado)
  • Re: Communicating over the internet
    ... > That way you provide one manner in which to open the database, ... > can keep the connection open and then when someone wants to ... > server as the database and the soap dll connecting with a TCP socket. ... The name of the running program might help. ...
    (microsoft.public.vb.general.discussion)
  • Re: ADO Connection Timeout
    ... much rather write stored procedures and use server side cursors. ... local database, it is vital that I get the information to a central server. ... Once the connection is restored, ...
    (microsoft.public.data.ado)