yechan
asked on
Identify when a connection was lost
Hi,
I have a SQL Server box and when executing sql statements it usually returns with data but every great once in a while I am getting a connection timeout error. Is there a way to find out when a network connection was lost and/or restablished? SQL is running on Windows Server 2008.
thank you
I have a SQL Server box and when executing sql statements it usually returns with data but every great once in a while I am getting a connection timeout error. Is there a way to find out when a network connection was lost and/or restablished? SQL is running on Windows Server 2008.
thank you
ASKER
hi lcohan,
The timeouts are a result of running unit tests on a bamboo server. The database itself is not very transactional and also it will be run against our test database, thus, not too worried about bringing down SQL Server. Do you know how to configure profiler so that it captures only lost/restablished network connections?
The timeouts are a result of running unit tests on a bamboo server. The database itself is not very transactional and also it will be run against our test database, thus, not too worried about bringing down SQL Server. Do you know how to configure profiler so that it captures only lost/restablished network connections?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you chief. This is a really cool tool.
WIN 7 ALSO OFFERS THAT TOOL... SO YOU CAN USE IT TO TROUBLESHOOT YOUR W7 DESKTOP COMPUTERS.
Where is the timeout coming from?? SQL code object or outside sql app code?
You could change the SQL query timeout from default 600 seconds in 2005/2008 to 0 or unlimited but CAUTION don't just do that in a production SQL server. This way the queries will never timeout in SQL but connections may be still chopped from the app - connection timeouts or other defaults.
"Is there a way to find out when a network connection was lost and/or restablished?"
Yes, you can use SQL profiler for that but CAUTION again because if you just start a default trace AS IS against a busy production SQL server you may bring it down.