ASP/Access 2000 over the Web robust?

[balance]

A call to people who have built Websites using ASP and Access 2000.

With the development and availability of PHP and mySQL most of my development has been in these languages, is Access considered a decent backend to a low hit website? Are there issues with how many connections can be maintained at once? Are there issues when this grows? What is the threshold of these issues?

Any general comments about your experiences with Access over the Web?

Any URLs of sites that are built with ASP/Access?

Thank you so much for any feedback,

Balance

 

[palbano]

I have several low usage sites using Access 2000 files. Access versions before 2000 were horrible. Low usage of Access 2000 is very robust. I don’t know what the usage threshold is but I would guess pretty low. Also the size of the files effects performance dramatically. You might want to test files above 2 meg in size and see what the performance is like. The bottom line is, if you need large database(s) or handle anything above low volume traffic you should not consider using a desktop database.

-pete

 

[Ayac]

It all depends on how you implement your code and how strong your server is.
Low traffic websites, where you do not run overcomplicated SQL commands, Access is just fine. We have a search engine hitting an Access database of 20.000 records, looking at about eight, 255 character long fields simultaneously and it works fine. Our site has an average of 3 hits/second.

However, we have a calendar system using lots of "UNION SELECT" commands, getting information from our backoffice system, plus using its own access tables of 100 individuals and it takes about 8 minutes to create a report with all the events displayed and it slows down the server very badly...

If you build your own content management system using a few hundred pages, Access is not worse than anything else...

 

[lebisol]

this is a post from howtomx.com....I forgot the user name but credit goes this "Mr.?"
------------------------------------
General ADO Tip

1. Don’t create a recordset unless it’s required.
2. Pick only the column you need avoid select *.
3. Use stored procedures as much as possible.
4. Use the appropriate cursor and lock mode the less work ADO has to do maintaining a details about records and locking, the faster the performance
5. Use stored procedures for data changes.

Database design

1. Use indexing
2. Avoid table scan
3. use Database statistic for SQL Server (see update statistics in the SQL book)
4. Use Access for desktop SQL server for enterprise

Data Caching

1. For lookup data use the GetRows method of a recordset and convert the recordset into an array.
2. Use data shaping
3. Since the default cache size of a recordset is set to 1. Increase this cache size will surely speedup your record set . change rsYourResordset.Cachesize = 10 rather than 1

Code Optimizing

1. The usual

Unoptimized code

While NOT rsMyRecord.EOF
Response.write rsMyrecord(“FirstName”) & “ “ & rsMy.Record(“LastName”)
Wend

Optimized code

Set FirstName = rsMyRecord(“FirstName”)
Set LastName = rsMyrRecord(“LastName”)
While NOT rsMyRecord.EOF
Response.write FirstName & “ “ & LastName
Wend

2. Avoid <%% > swiching between ASP code and HTML minimize script block transitions
3. Avoid session variable
4. Avoid nested includes
5. Don’t mix script engines Jsscript versus VBScript
6. Turn off script debugging
------------------------------

I have seen Access outrun any other DB in its class !!!
I have seen it chrash due to the fact ...that is tuesday
All the best