Access database for web application

[csgraham74]

Hi guys,

I was wondering if someone could help me.

Im in the process of building a web site in asp.net that uses MS Access
as the backend for the site.

I have heard numerous people say that access is not a good backend
database for web applications as there are locking issues and
performance issues.

The database im building will at most only have a couple of thousand
records.

My main concern is the connection that im using - in regards to locking
out other users. I have used access extensively as bound database but
not in this unbound mode and therefore i need help.

If anyone can enlighten me on this subject or point me in the right
direction in regards to best practice i would appreciate it.

Thanks

CG

 

[david epsom dot com dot au]

Access is not a good database for web applications
because you typically have to take it offline to
do backups and upgrades.

In fact with IISAPI you had to close the webserver to
take the MDB offline to do backups and upgrades.

Access is also not a good database for web applications
because it is not really supported by MS for that
kind of application.

Also, you have to be very careful to handle threading
correctly one way is to set jet to be single threaded,
but you can only do that if you have control of the server.
The other way is to make sure that there is only a
single thread that calls jet. If you aren't careful,
under heavy load you may get thread creation errors.

The only performance issue is that it doesn't easily
scale to multiple servers.

I don't know about locking problems. I never had any.

(david)

 

[SupportX]

Subject: RE: Re: Access database for web application



-----Original Message-----