May 25, 2009 at 6:34 am
We have a requirement to develop a service to monitor Sql Server initiated Connection Rejections.
Can you please shower your inputs on the Sql Server Initiated Rejections concept, support in Sql Server 2005?
Following is an example scenario
1)There is a Sql Server 2005 Database Machine (machine#1)
2)There is another machine (machine#2). It can be a Windows Machine or Linux Machine
There is a client application in machine#2 which is using Database of machine#1. The Database connection is working fine till some time. Later at some point of time, due to some reasons Sql Server has rejected the Database connection of this client application. The client application may not know this connection rejected/lost.
We have to come up with an approach to monitor this kind of rejected connections, connections lost (Which are not known to Client Application). This service will be residing in Sql server machine.
The main thing to be noted here the trigger for connection rejection is from Sql Server and Client application is unaware of the same. The another kind of connection failures where Client application is aware of like timeout during connections are generally handled in client applications, so we don’t need to concentrate about the second kind.
thanks much.
May 25, 2009 at 10:10 am
I'm not aware of connection rejections as a concept. SQL Server might terminate a connection on a fatal error, but otherwise it is the client that terminates connections.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply