Performance questions on SQL Server 2K

Hello, all. We were directed by Mark Schupp in the ASP newsgroup
(microsoft.public.inetserver.asp.general) to post this here and see if
anyone has an answer. He thought it might be a problem with the SQL Server
and not the web server. The apps with problems hit our SQL Server 2K across
the network. We've had occasions where we get Timeout Expired errors in some
of our ASP apps, and non-ASP vendor apps on separate servers that hit the
SQL Server get into the same problem of hourglassing and not coming back.
When the admins reboot the SQL Server machine, it clears it up for awhile.
What we're wondering is this: Is it the web server, the network, or the SQL
Server that is creating this headache? During the times when we've had those
issues, we've immediately started running the Performance Monitor to see if
we can track the issue, with the following counters added:
- Request Wait Time (ASP)
- Requests Executing (ASP)
- Requests Timed Out (ASP)
- Pages/sec. (Memory)
- % Processor Time
We didn't see the above items spike during the times users were getting the
Timeout Expired errors. How can we look at one individual ASP application to
see if we can rule it out as the culprit? Also, how can we tell if this is
caused by the network or the database server?
Thanks.SQL Server Profiler is your tool.
"dw" <cougarmana_NOSPAM@.uncw.edu> wrote in message
news:%23Dgw9kNnEHA.1800@.TK2MSFTNGP15.phx.gbl...
> Hello, all. We were directed by Mark Schupp in the ASP newsgroup
> (microsoft.public.inetserver.asp.general) to post this here and see if
> anyone has an answer. He thought it might be a problem with the SQL Server
> and not the web server. The apps with problems hit our SQL Server 2K
across
> the network. We've had occasions where we get Timeout Expired errors in
some
> of our ASP apps, and non-ASP vendor apps on separate servers that hit the
> SQL Server get into the same problem of hourglassing and not coming back.
> When the admins reboot the SQL Server machine, it clears it up for awhile.
> What we're wondering is this: Is it the web server, the network, or the
SQL
> Server that is creating this headache? During the times when we've had
those
> issues, we've immediately started running the Performance Monitor to see
if
> we can track the issue, with the following counters added:
> - Request Wait Time (ASP)
> - Requests Executing (ASP)
> - Requests Timed Out (ASP)
> - Pages/sec. (Memory)
> - % Processor Time
> We didn't see the above items spike during the times users were getting
the
> Timeout Expired errors. How can we look at one individual ASP application
to
> see if we can rule it out as the culprit? Also, how can we tell if this is
> caused by the network or the database server?
> Thanks.
>
>