Timeouts are defined by the connection. You won't find them on the DB server, you need to capture them in the App server which is the one getting the timeouts.
Luis Cazares - Tuesday, February 14, 2017 6:25 AM
sure, thank you!
As you can see I have some timeouts in sql logs from sql agent - jobs like update stats or checkdb.
[...] LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). [...]
moreover... for example checkdb - first time failed with oledb errror, the next one with success[/url]
Is there any app to trace connection errors with issue details etc?
Connection timeouts are very hard to track. They're almost impossible to track within SQL Server because they're not connecting, therefore, SQL Server doesn't see anything. You just can't track what's not there. Generally, you'll need to track this issue from the outside, network management tools, etc. I don't have a good, specific, suggestion on it.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply