Over the last couple of days we have had issues where db-intensive applications are running slow. I have used ( to the best of my ability ) tools such as DebugDiag and IIS Tracing and perfmon to come to the conclusion that the reason is most likely the website not closing connections cleanly.
I know that this can be determined by a code-review, how can i as an IIS administrator determine the "faulty" query/code from an infrastructure perspective.
I understand that a SQL Profiler can be run on the database to determine the offending thread, but i would like to understand what i can do from the IIS server to get a more definitive answer. From my investigation so far i have been able to determine the page but not the function on the page that is causing the delay.
