SP timing out, can't find the cause

We are using SQL Server 2005. The SP in question is a fairly simple
select statement. When the developers run their unit tests it is
timing out (15 second timeout is set from their end). When I run the
SP in a query window using the exact same parameters it takes less
than a second to run. I've run profiler and turned up nothing there,
including deadlocks. The SP does show as having a duration of 15
seconds though. I've also run the blocking monitor as described on
Microsoft's site (http://support.microsoft.com/kb/271509) and I don't
see any blocking issues. I've also monitored CPU and IO access times
through the performance monitor on the server and everything looked
clear.

Is there something obvious that I should be checking? I'm at a loss
(and a bit rusty in my performance monitoring).

Thanks!
-Tom.
.

Relevant Pages

  • Re: Batch Requests/Sec counter
    ... The performance monitor shows it at the scale of 1000 so ... >I support the Professional Association for SQL Server ... >> The batch requests per second shown on the performance ... network card is only ...
    (microsoft.public.sqlserver.server)
  • Re: performance monitor
    ... Both performance monitor and SQL Profiler can monitor remote machines. ... With SQL Profiler, when you launch it, you just choose the SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: Monitor Transaction log
    ... On the client end you can poll to queue ... >>> Is there a way to monitor transaction log in SQL server and Oracle ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Batch Requests/Sec counter
    ... The scale on performance monitor only affects the position of the graph. ... I support the Professional Association for SQL Server ... >>> The batch requests per second shown on the performance ...
    (microsoft.public.sqlserver.server)
  • Re: SP timing out, cant find the cause
    ... timing out (15 second timeout is set from their end). ... I've also run the blocking monitor as described on ... through the performance monitor on the server and everything looked ...
    (comp.databases.ms-sqlserver)