W2K Server ASP MDB Error

Hi all,
I live some problems with our Windows 2000 Server abour some ASP pages who use MDB connection.

For example; please chech this page: http://www.bursasporum.com. As u see this page comes too slow. When you visit this site i will hear a sound from SCSI HDD for 10 sec. Also if you visit: http://www.bursasporum.com/forum u will see this page will come 2 fast. Both of pages uses ASP and MDB connection. There is no different.

Also i live same problems about other sites who uses ASP and MDB connection on our server. We can't understand what is wrong.

Anyway, in Event Viewer there is no Error messages. So that is why i will go crazy about this.

When a visitor visits a web site who use asp + mdb connection i hear a sound from hdd. It takes avarage 10 second, when it stops (sound) visitor see page... !!

But when a visitor visits forum page there is no problem. It comes too fast. I think it is about ODBC but forum uses ODBC too but there is no problem. Is there any idea about this?

Regards

 

My first comment is that by going by the sophistication of the javascript within your pages, I think your desciption of your skills as beginner is at least disengenuous.

Second, I think the way you are encouraging people to connect to your website would raise the suspicions of any knowledgable user of the internet who is aware of the widespread use of dodgy websites to spread IE exploits. You are in effect encouraging users to access an untrusted website.

Third, the chance of anyone being able to diagnose the nature of your problem without access to your server config, logs, and ASP source code is limited in the extreme.

Therefore, this looks dodgy to me in the extreme. I would recommend that you repost with information that could be used to diagnose the problem and without links that encourage users to use bad practice.

 

ReggieB - The 'beginner' experience level could easily be a language/cultural thing.

I know somewhere around zero on this topic but if there is info he could post that would help, maybe you could specify what sort of thing should be included.

 

You should start by perfmon'ing your machine during a hit and see what is going on. Is your ASP script causing a tablescan, or using unindexed columns?

You need to determine what component the delay is coming from. As it stands right now, we have nowhere near enough information to assist you. You could have anything from bad design, corrupted indexes, using too large an mdb, a heavily fragmented hard drive, an overtaxed CPU.. tons of things.

I'd recommend you consider giving microsoft a call on this one. They can help you through identifying the source of the 10 second delay and advise you on how to fix it.