Connections

[Alberto Poblacion]

If you only need the connection briefly to read a few data, then spend a lot
of time processing these data, and then need the connection briefly again,
then it is better to close the connection while it is not in use. In this
way you free the server to use the connection for other processes, and if
every program does this the total nuber of connections needed on the server
will be smaller than if every process keeps the connections open all the
time. Don't worry about the overhead of "reopening" the connection when you
need it again; the connection pool will automatically take care of
minimizing the actual opening and closing of connections.

 

[DaveP]

im writing a service that will be on a app server
this is one of many service's to process Recordsets from Sql Server...
1 service may have 20 Processes to Complete
example
main class PreProcess()
method CleanNames();
method updateNames();
methodr ValidateContracts();
Various things must be completed
Suedo Example below
My question is
in the main class make my connection and keep it for all sub members
or connect in each member
A. This Way opens connection...closes connect

method cleanNames()
1 get connection
2 get recordset
3. Close Connection
4 process Recordset
5. Open Connection
4 Commit Changes
6. Close Connection()
finished cleanames()
or
method cleanNames()
1 get connection
2 get recordset
3 process Recordset
4 Commit Changes
5. Close Connection()
finished cleanames()
or
this final way is in the parent Class or Calling Function
sends in the connections holds it open till the service is
completed of all jobs its Suppose to do
then releases the connection

method cleanNames(oconn) connection as parameter
1 get recordset
2 process Recordset
3 Commit Changes
finished cleanames()

Thanks
DaveP

 

[DaveP]

Thanks Alerto
daveP

If you only need the connection briefly to read a few data, then spend a
lot of time processing these data, and then need the connection briefly
again, then it is better to close the connection while it is not in use.
In this way you free the server to use the connection for other processes,
and if every program does this the total nuber of connections needed on
the server will be smaller than if every process keeps the connections
open all the time. Don't worry about the overhead of "reopening" the
connection when you need it again; the connection pool will automatically
take care of minimizing the actual opening and closing of connections.