Today I'm looking at a few Watson dumps trying to determine why SqlConnection is failing to connect to SQL Server and hanging. I see stack like below: 0:000> k 0021dc5c 79f40778 kernel32!SleepEx+0x62 0021dc90 7a0561d7 mscorwks!EESleepEx+0xa3 0021dc9c
Read More...
If you have pooling issues with ADO.NET (leaking connections, pool size exceeded, etc...) one way to slice and dice these with SQL 2005 is to use the SQL 2005 system DMVs. You can locate leaked connections like so: select session_id, datediff(s,last_read,getdate())
Read More...
