HiveBrain v1.2.0
Get Started
← Back to all entries
patternsqlMinor

Tracking Down Application Timeout Errors in SQL Server

Submitted by: @import:stackexchange-dba··
0
Viewed 0 times
trackingapplicationsqltimeoutdownservererrors

Problem

SQL Server 2008 SP3

How do I track down these timeout errors ?

The errors are displayed on an intranet dashboard used specifically for error reporting in IIS. My suspicion is that there is a default timeout of 30 seconds in the web application and if a query takes more than thirty seconds, an exception is thrown. As there are many queries that take longer than 30 seconds on these SQL servers, I can't just filter in profiler based on duration.

Serving up the website being monitored by this dashboard are two IIS servers retrieving data from seven SQL Server instances.

Could I use the "User Error Message Event" and the "OLEDB Errors Event" to track these errors in SQL Server Profiler?

Solution

Aaron Bertrand put me on the right track with his comment


And I believe you should be able to filter on duration and error <> 0.

Created a server side trace using the tsql_duration profile template

-
Added the User Error Message Event

-
Added the following filters

error <> 0

error <> 1

severity <> 10

This avoided capturing the USE DATABASE commands

The error message captured by profiler was 2 - Abort and the Event Class was 10 RPC:Completed.

Context

StackExchange Database Administrators Q#80165, answer score: 7

Revisions (0)

No revisions yet.