8

I'm trying to find SQL statements that timed out using the SQL 2005 profiler. Is there a way to set such a filter?

Ron Harlev
  • 16,227
  • 24
  • 89
  • 132

3 Answers3

8

In Profiler, you can add the event "Attention" under "Errors and Warnings". It's definition is

Collects all attention events, such as client interrupt request or when a client connection is broken.

As far as other errors (deadlocks, contraints, etc), try "Execution Warning" (reports warning that occurred during the execution of SQL statement or procedure) or "User Error Message" (the error message displayed to the user in the case of an error or exception).

jons911
  • 1,836
  • 15
  • 19
1

Yes.

  • Check "All Events"
  • Go to the lock section
  • Specify the "lock: Timeout" events

Lock event in Books Online

Now, this works with server side locks (@@LOCK_TIMEOUT <> 0). I don't know if a client side timeout will be trapped.

gbn
  • 422,506
  • 82
  • 585
  • 676
  • 3
    This will only catch timeouts caused by locking. Long running queries timed out by the calling application will not necessarily have locking issues. – jons911 Nov 11 '08 at 15:15
0

One option, if you know what your client configured timeouts are set to (ie. 30 seconds by default), you can set a filter on your trace to only collect events with a duration greater than or equal to your timeout (minus a second or two).

John Lemp
  • 5,029
  • 3
  • 28
  • 36