Forum Moderators: phranque
I am using Access database to store my dynamic pages information, like products, categories, customers, sales, etc.
I have no problem what so ever running it on WIN NT 4 / IIS4 at my hosting company, I also have no problem running from home using Windows 2000 Pro / IIS5.
I am in the process of changing to Windows 2000 hosting,
I ran in a problem where when I try to display data from the database it bring the server down to its knees, it just happen every time I try that.
What I am trying to find out is the following:
Does IIS5 configurations has any thing to do with it?
Does SQL query has any limitations on the number of fields returned from INNER JOINT of 2 tables?
Also any other information is appreciated.
Thank you.
Take a look through the Microsoft forum as well for more information.
Access can't handle too many connections at once, and leaves too many open objects.
I had the same problem and when I ditched Access in favor of mySQL all my problems (at least for serving pages) went away.
That is my next step to use mySQL, but what is bugging me is the code has been working for the last year on NT4, and it has been tested on Win 2000. I know it has to be something with the settings on the new server.
Thanks for the quick response.
There are some differences/defaults between IIS4 and IIS5 regarding process isolation. So it might be worth while to compare the two configurations. Running the application with the low option in IIS 5 is similar to running the app in IIS4 with the separate process option unchecked. Selecting the high option in IIS5 is similar to having the separate process option checked in IIS4.
Also make sure to identify any other differences between the two environments. Do they both have the same version of Access installed? Same Db? What about the hardware, such as memory, cpu, disk size and speed, etc. How about the database drivers, are they the same?
Does the app actually return any data [albeit very slow] or does it return an error message?
Performance monitor might be able to shed some light on the performance bottleneck. Some metrics worth watching might be cpu usage, disk access, page faults, and memory consumption; Which could be used for comparison with the existing application.
Sorry I don't have any specifics, but it really could almost be anything at this point. So, check that the environments are as close as possible and note any differences. This in conjunction with some metric results might help point us in the right direction...
I figured out the problem, I was joining 2 tables with one field in both tables named CatCode, and when I was trying to use that field it was getting confused on which one I wanted.
But the funny thing, that code has been running on NT4/IIS4 for about 2 years with out any problems.
JuniorHarris,
You are right about the configuration and what version of access you are running.
