August 21, 2014 at 3:05 am
Hi there - We experienced a number of SQL times outs yesterday.
I have the code which timed out but I can't find the root cause.
I have scanned through the error logs but can't see any issues with the OS/application.
Is there a DMV which would store timeout issues which could help me in finding the root cause, or is there a DMV which shows historic locking/deadlock without running a SQL trace?
Thanks!
--------------------------------------------
Laughing in the face of contention...
August 21, 2014 at 3:19 am
No to all
Timeout is not a SQL concept, so it wouldn't store that anyway. Timeout occurs when the application decides it's waited too long and signals SQL to stop processing.
If you've got the queries that were timing out, then that's where you start, with testing their performance out on a test server (one that has a copy of the prod database)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2014 at 3:45 am
Ok, thanks. Thought as much but wanted to double check. Thanks again!
--------------------------------------------
Laughing in the face of contention...
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply