BorlandTalk.com

David Freeman · Guest

Using Delphi 7 Professional...

Currently I set myadoconnection.open at the start of my program and .close
at the end of the program. This means that the user has the connection open
all day. I have not had any problems with this and, at least with AS/400s,
this has a huge performance benefit.

However, I am now using SQL Server and read that this is not the best
option. I read that I should open the adoconnection before each select and
close it immediately after. (I assume that the open .. close should enclose
a transaction?)

My question: When using SQL Server 2005, should I have the
adoconnection.open only for the brief periods where it is needed?

Many thanks
David

Del Murray · Guest

It depends on the type of application but in general the answer is NO. Sql
server will manage all the open connections and roll out the inactive ones
if they are not used.

This is not true if you use multiple connections to SQL Server. If you use
ADO and you create 3 tADODataSets and put a connection string in each object
you will soon find yourself in connection hell. Use a tADOConnection, rout
all other data objects thru that connection , open it at startup, close it
at shutdown.

There are about as many opinions about this as there are programmers .. All
I can say is, this works great for me, others may have some better ideas
that I haven't learned about in the last 10 years.

Del

David Freeman · Guest

Thanks for your quick reply Del. Your comments match what I was thinking.

(as an aside, I am only using tadoquery and tadocommand for my i/o)

regards
David

Del Murray · Guest

try sticking to tadoDataSet .. tadoQuery was only for backward compatibility
to Delphi 3