|
|||||||||
|
|||||||||
|
|||||||||
 |
|||||||||
| |
||
|
|
|
|
|||||||||
|
|||||||||
|
|||||||||
|
|||||||||
| |
||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
ASP Free Forums Sponsor:
|
|
|
|
#1
April 7th, 2004, 09:25 AM
|
|||
|
|||
|
IIS 5.0 request handling issue.
I have a strange problem. In SQL SERVER 2000 when a stored procedure having a statement "WAITFOR DELAY 00:00:05" is called by multiple users simultaneously,then each request is executed as a separate thread and all of them get the result almost simultaneously. But when the same stored procedure is called by an ASP page through IIS by say 10 users simultaneously then each request is queued and they are served in the order First Come First Serve . IIS 5.0 is supposed to be multithreaded and each request is supposed to be handled by a separate thread. But i want to know why each request is queued and not executed simulataneously
|
|
#3
April 7th, 2004, 07:52 PM
|
|||
|
|||
|
Because unless your web users are authenticated to windows, IIS is servicing them all under one user context which effectively serializes database access.
That's my guess, anyway 
__________________
====== Doug G ====== I didn't attend the funeral, but I sent a nice letter saying I approved of it. --Mark Twain
|
|
| Viewing: ASP Free Forums > System Administration > Microsoft IIS > IIS 5.0 request handling issue. |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
|
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
