MS Access - Connection Pooling?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

Does the same rule valid for OleDbConnection for MS Access, as it is a case
with SQL Server, to open connection, and close it immediatly after usage? Or
for MS Access, connection sould be opened during whole application run?

Thanks
 
MilanB,

The OleDB provider for Access supports connection pooling. So you can open a
connection immediately before use and close it immediately after use without
much of a performance penalty and for a scalability benefit (if Access can be
considered appropriate for scalable apps).

Kerry Moorman
 
¤ Hello,
¤
¤ Does the same rule valid for OleDbConnection for MS Access, as it is a case
¤ with SQL Server, to open connection, and close it immediatly after usage? Or
¤ for MS Access, connection sould be opened during whole application run?

Connection pooling is almost meaningless for the Jet database engine since there is very little
overhead and almost all connections occur on the client.

Open and close your connections on an "as needed" basis for an Access database.


Paul
~~~~
Microsoft MVP (Visual Basic)
 
I agree, connection pooling in Access for performance reasons is like "why
bother". Though what about running multiple queries on the same connection?
You can't do that, so you still need some connection management routine in
place.

SM
 
Back
Top