TADOConnection does not close connection on SQL Server until destroyed?

Thread View: borland.public.cppbuilder.database.ado

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Piero Salandin Mon, 09 Apr 2001 10:03

#5537

Author: Piero Salandin
Date: Mon, 09 Apr 2001 10:03

15 lines
1336 bytes

C++Builder 5 Enterprise on W98

I tried the behaviour of a TADOConnection with MS Sql Server, and using the
SQL Server Profiler I saw that the connection does not really closes when I
issue a TADOConn->Close() but only when I end the application (and the
DataModule is removed from memory).

Anyone can explain me why?

Thanks a lot


--
Ing. Piero Salandin
piero.salandin@libero.it

Re: TADOConnection does not close connection on SQL Server until destroyed?

#5545

Author: Mehrdad Momeni
Date: Mon, 09 Apr 2001 17:07

34 lines
1777 bytes

Hi Piero

ADO has a caching mechanism on its connections. By default this cache works
(and gives performance benifits). If you insist, you can turn off the cache
by including somthing like "OLE DB SERVICES = 0" in the connection string of
your TADOConnection.

erAdat
Mehrdad

"Piero Salandin" <piero.salandin@libero.it> wrote in message
news:3ad1a320_1@dnews...
> C++Builder 5 Enterprise on W98
>
> I tried the behaviour of a TADOConnection with MS Sql Server, and using
the
> SQL Server Profiler I saw that the connection does not really closes when
I
> issue a TADOConn->Close() but only when I end the application (and the
> DataModule is removed from memory).
>
> Anyone can explain me why?
>
> Thanks a lot
>
>
> --
> Ing. Piero Salandin
> piero.salandin@libero.it
>
>
>
>
>

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads