February 17, 2005 at 10:46 am
I have a management request to 'prove' that a current problem isnt caused by SQL Server kicking user connections off the system.
Is there a way to log the reason a connection ends?
This is a production box that has connections coming in from another server hosting a web application. The Web application server had a problem and they would like to blame the database. I dont think the issue is related to the DB at all, but the web server log does show a large number of connection attempts by the application just before the crash.
If I cant show historically how connections are broken, an ongoing solution would be good.
thanks in advance
February 21, 2005 at 9:15 pm
Check sql error log near the moment of crash for historical records.
Setup alert on connection number may be used for ongoing base.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply