Access Database draw backs

[bleak26]

I have some security issues with a website designed by someone else that i have been asked to update. The site is ASP and it's using an Access Database. The access database is in the root of the site and can be accessed simple by specifiying the file name and the url. How can i go about securing it? Also on a side note could you tell me if access databases will stand up to heavy load from users of the site?

[txbakers]

If you move the database out of the internet path, it won't be accessible over the web. That's rule #1 of database/web security.

Also, Access databases aren't designed for heavy web work. They are good for desktop/intranet applications, but won't hold up under the internet stress.

Look to something like mySQL, postGreSql, or the big boys MSSQL, etc.

[Easy_Coder]

Also on a side note could you tell me if access databases will stand up to heavy load from users of the site?

How heavy? Access has a limitation of 255 concurrent connections.

[KeywordROI]

Access has a limitation of 255 concurrent connections.

But only 1 write connection. While one user is writing to the database, not one else can even read it.

Imagine using that for a hit counter. Argh...

[johnhh]

Are you using a DNS-less connection string or a DNS reference on the ASP connection?

For any work of any volume forget access use mysql or Microsoft SQLServer ( *nix platform or Microsoft server platform respectively )

Best have the database away from the root directory - as previously stated.

255 connections is the theoretical maximum but under load try 5 as a max!

[aspdaddy]

You can also corrupt the database with more than 3 or 4 concurrent write connections. But for read only content serving its cheap, easy to use and should be ok for 500 uniques per day.