Last post Nov 27, 2007 10:21 PM by OWScott
Nov 27, 2007 05:01 PM|accelerator|LINK
Sorry to ask a Windows 2000 Advanced Server question here but I couldn't think of where else to post. I have a Windows 2000 Advanced Server where there's a performance issue with some of the .asp pages (i.e. classic asp) that retrieve data from Access databases,
(I know Access databases aren't ideal for data). These pages will just get stuck/freeze, and then either suddenly spring back to life, or give a script timeout error 0113.
The largest Access database I've seen is 136MB (is that way too large?)
I will probably move some of the large Access databases onto a different server but before I do:
- Are there any tools you can recommend to diagnose exactly what files / databases are causing the problem. I don't think the Win 2000 performance monitor tools even work.
- Can anyone explain more about the technicalities behind this issue. I expect it has something to do with processes, threads, memory, Access drivers being loaded into memory etc etc. Can anyone tell me what they know to put me in the picture better?
Nov 27, 2007 10:21 PM|OWScott|LINK
Access was never build for web related use where there would be multiple simultaneous connections to the data database. It's best suited for a winforms app on a local server. That said,
it's served people well for years, but only to a point. It's about 30ish simultaneous connections where Access will start to break and it will get worse as the database grows. A 136MB database isn't that large, but if most of the space is from a small number
of tables and multiple users are making page requests that are querying that database at the same time, that could run into an issue quickly.
IISState is a good tool to get some visibility into the issue. If you install it and run it from the command line when the issue occurs, you'll see if there are any locks waiting on the