Hi, I have a weird problem I was hoping someone could shed some light on.
Currently I have a .aspx search screen on a webserver (4 cpu) that acesses
an sql database on our database server (4 cpu). It is used to search for
people in the database.
The problem is, on a query of say 's' for a last name, the search will union
on a number of different searches one of them being '%s%' which brings back a
rather large set of rows using a data reader. From there, we do relevance
processing, listing the person's brought back in order of greatest relevance
to search criteria.
On a rather large search like this, the database server does not seem to be
impacted much, but the webserver is hit hard. All other concurrent users
notice an immediate impact. Also, once the person that executed the original
query closes the browser without using the logout button, the server is still
affected for about 20 minutes. All of the timeouts on sessions, and ADO
commands have been left as default.
Any ideas why there is such an impact?
Also, what is responsible for killing the session on the server when a
person closes the browser? is there a way of explicitly enforcing this?
Would a dataset have less impact?
Any help is greatly appreciated,
Joester
