Re: Handling connections to MS Access database

mbanavige — Fri, 26 Jun 2009 23:07:43 GMT

The technique that is generally preferred is to:

Open the db connection as late as possible
Close that db connection as soon as possible

This means, do not open your db connection until you are ready to execute a statement against the db and then immediately after accessing your db, you would want to close that connection.

AnnaMaria:
But is it ok to open a new connection for each SQL command?

Yes - .NET will handle connection pooling for you so that performance won't suffer.

Handling connections to MS Access database

AnnaMaria — Fri, 26 Jun 2009 22:26:01 GMT

Hallo,

I'm developing a web interface to a MS Access database with ASP.NET 3.5. There are about 10 users. I guess that each of them will have a look into the database 20 times per day and will add about 20 new records per day.

Now I'm thinking about the best way to handle the connections to the database.

Keeping a single connection during the whole session does not seem to be a good idea as a session might last a whole day.

But is it ok to open a new connection for each SQL command?

Is there any other possibility?

Thanks in advance,

Anna

Access Databases and AccessDataSource Control

Re: Handling connections to MS Access database

Handling connections to MS Access database