IIS 6 vs IIS 5 ASP.NET Performance Issues

[JMaelstrom]

I have currently developed an intranet asp.net (v1.1.4322 framework)
app on a Windows XP Pro machine running IIS 5 with all patches. The
backend is an Access database utilizing ADO.NET.

My problem is the app runs perfectly on IIS 5, but when moved to
production on a Windows 2003 box running IIS 6 (v1.1.4322 framework)
with all patches (and ample hardware), performance degrades to the
point the app is almost useless.

The slow down is occurring during database access on both the local
machine and remote machines. I know that many will point out that the
database and access to it needs analyzed to see if it is the culprit,
but it runs perfect under IIS 5, so it is definitely something with
Win2k3 / IIS 6, or both.

I have read several posts stating that using basic authentication and
changing it to IIS 5 isolation mode would do the trick, but that
wasn't the case.

I've also read that specifically setting the datatype of the paramters
on an update (rather than allowing the Dataset to do it) can improve
performance. The issue with that fix, and the reason why I'm not going
this route, is that it is not a problem under IIS 5, only IIS 6, and
is obviously an IIS / Win2k3 issue, and not a coding issue.

It may be an IIS setting or an application setting that isn't obvious.
Whatever the case, I'm completely frazzled...

This is an issue that needs resolved ASAP, as we can't fallback to IIS
5...

Any help would be greatly appreciated!

Thanks in advance

 

[rattatosk]

ASP IIS5 versus IIS6

Hi,
we are experiencing the same problem.

Dit you manage to solve this problem ?

Greetings
Arnout

 

[shan420]

MS ACCESS the slowest

hi there,

i would recommend you to use MS SQL free express edition, and use stored procedures. We have used MS Access in many different places, and it's not a real DB, extremely slow performance.

I have currently developed an intranet asp.net (v1.1.4322 framework)
app on a Windows XP Pro machine running IIS 5 with all patches. The
backend is an Access database utilizing ADO.NET.

My problem is the app runs perfectly on IIS 5, but when moved to
production on a Windows 2003 box running IIS 6 (v1.1.4322 framework)
with all patches (and ample hardware), performance degrades to the
point the app is almost useless.

The slow down is occurring during database access on both the local
machine and remote machines. I know that many will point out that the
database and access to it needs analyzed to see if it is the culprit,
but it runs perfect under IIS 5, so it is definitely something with
Win2k3 / IIS 6, or both.

I have read several posts stating that using basic authentication and
changing it to IIS 5 isolation mode would do the trick, but that
wasn't the case.

I've also read that specifically setting the datatype of the paramters
on an update (rather than allowing the Dataset to do it) can improve
performance. The issue with that fix, and the reason why I'm not going
this route, is that it is not a problem under IIS 5, only IIS 6, and
is obviously an IIS / Win2k3 issue, and not a coding issue.

It may be an IIS setting or an application setting that isn't obvious.
Whatever the case, I'm completely frazzled...

This is an issue that needs resolved ASAP, as we can't fallback to IIS
5...

Any help would be greatly appreciated!

Thanks in advance